View E702196SH7750_1439477.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

regarding the change of names mentioned in the document, such as hitachi electric and hitachi xx, to renesas technology corp. the semiconductor operations of mitsubishi electric and hitachi were transferred to renesas technology corporation on april 1st 2003. these operations include microcomputer, logic, analog and discrete devices, and memory chips other than drams (flash memory, srams etc.) accordingly, although hitachi, hitachi, ltd., hitachi semiconductors, and other hitachi brand names are mentioned in the document, these names have in fact all been changed to renesas technology corp. thank you for your understanding. except for our corporate trademark, logo and corporate statement, no changes whatsoever have been made to the contents of the document, and these changes do not constitute any alteration to the contents of the document itself. renesas technology home page: http://www.renesas.com renesas technology corp. customer support dept. april 1, 2003 to all our customers
cautions keep safety first in your circuit designs! 1. renesas technology corporation puts the maximum effort into making semiconductor products better and more reliable, but there is always the possibility that trouble may occur with them. trouble with semiconductors may lead to personal injury, fire or property damage. remember to give due consideration to safety when making your circuit designs, with appropriate measures such as (i) placement of substitutive, auxiliary circuits, (ii) use of nonflammable material or (iii) prevention against any malfunction or mishap. notes regarding these materials 1. these materials are intended as a reference to assist our customers in the selection of the renesas technology corporation product best suited to the customer's application; they do not convey any license under any intellectual property rights, or an y other rights, belonging to renesas technology corporation or a third party. 2. renesas technology corporation assumes no responsibility for any damage, or infringement of any third-party's rights, originating in the use of any product data, diagrams, charts, programs, algorithms, or circuit application examples contained i n these materials. 3. all information contained in these materials, including product data, diagrams, charts, programs and algorithms represents information on products at the time of publication of these materials, and are subject to change by renesas technology corporation without notice due to product improvements or other reasons. it is therefore recommended that customers contact renesas technology corporation or an authorized renesas technology corporation product distributor for the latest product information before purchasing a product listed herein. the information described here may contain technical inaccuracies or typographical errors. renesas technology corporation assumes no responsibility for any damage, liability, or other loss rising from these inaccuracies or errors. please also pay attention to information published by renesas technology corporation by various means, including the renesas technology corporation semiconductor home page (http://www.renesas.com). 4. when using any or all of the information contained in these materials, including product data, diagrams, charts, programs, an d algorithms, please be sure to evaluate all information as a total system before making a final decision on the applicability of the information and products. renesas technology corporation assumes no responsibility for any damage, liability or other loss resulting from the information contained herein. 5. renesas technology corporation semiconductors are not designed or manufactured for use in a device or system that is used under circumstances in which human life is potentially at stake. please contact renesas technology corporation or an authorized renesas technology corporation product distributor when considering the use of a product contained herein for any specific purposes, such as apparatus or systems for transportation, vehicular, medical, aerospace, nuclear, or undersea repeater use. 6. the prior written approval of renesas technology corporation is necessary to reprint or reproduce in whole or in part these materials. 7. if these products or technologies are subject to the japanese export control restrictions, they must be exported under a lice nse from the japanese government and cannot be imported into a country other than the approved destination. any diversion or reexport contrary to the export control laws and regulations of japan and/or the country of destination is prohibited. 8. please contact renesas technology corporation for further details on these materials or the products contained therein.
hs7750kcm01he hitachi microcomputer development environment system sh7750 e10a emulator user?s manual ade-702-196a rev. 2.0 01/15/01 hitachi, ltd.

cautions 1. hitachi neither warrants nor grants licenses of any rights of hitachi?s or any third party?s patent, copyright, trademark, or other intellectual property rights for information contained in this document. hitachi bears no responsibility for problems that may arise with third party?s rights, including intellectual property rights, in connection with use of the information contained in this document. 2. products and product specifications may be subject to change without notice. confirm that you have received the latest product standards or specifications before final design, purchase or use. 3. hitachi makes every attempt to ensure that its products are of high quality and reliability. however, contact hitachi?s sales office before using the product in an application that demands especially high quality and reliability or where its failure or malfunction may directly threaten human life or cause risk of bodily injury, such as aerospace, aeronautics, nuclear power, combustion control, transportation, traffic, safety equipment or medical equipment for life support. 4. design your application so that the product is used within the ranges guaranteed by hitachi particularly for maximum rating, operating supply voltage range, heat radiation characteristics, installation conditions and other characteristics. hitachi bears no responsibility for failure or damage when used beyond the guaranteed ranges. even within the guaranteed ranges, consider normally foreseeable failure rates or failure modes in semiconductor devices and employ systemic measures such as fail-safes, so that the equipment incorporating hitachi product does not cause bodily injury, fire or other consequential damage due to operation of the hitachi product. 5. this product is not designed to be radiation resistant. 6. no one is permitted to reproduce or duplicate, in any form, the whole or part of this document without written approval from hitachi. 7. contact hitachi?s sales office for any questions regarding this document or hitachi semiconductor products.

rev. 2.0, 01/01, page i of vi important information read first ? read this user's manual before using this emulator product. keep the user's manual handy for future reference. do not attempt to use the emulator product until you fully understand its mechanism. emulator product: throughout this document, the term "emulator product" shall be defined as the following products produced only by hitachi, ltd. excluding all subsidiary products. ? emulator ? user system interface cable the user system or a host computer is not included in this definition. purpose of the emulator product: this emulator product is a software and hardware development tool for systems employing the hitachi microcomputer. this emulator product must only be used for the above purpose. limited applications: this emulator product is not authorized for use in medical, atomic energy, aeronautical or space technology applications without consent of the appropriate officer of a hitachi sales company. such use includes, but is not limited to, use in life support systems. buyers of this emulator product must notify the relevant hitachi sales offices before planning to use the product in such applications. improvement policy: hitachi, ltd. (including its subsidiaries, hereafter collectively referred to as hitachi) pursues a policy of continuing improvement in design, performance, and safety of the emulator product. hitachi reserves the right to change, wholly or partially, the specifications, design, user's manual, and other documentation at any time without notice. target user of the emulator product: this emulator product should only be used by those who have carefully read and thoroughly understood the information and restrictions contained in the user's manual. do not attempt to use the emulator product until you fully understand its mechanism. it is highly recommended that first-time users be instructed by users that are well versed in the operation of the emulator product.
rev. 2.0, 01/01, page ii of vi limited warranty hitachi warrants its emulator products to be manufactured in accordance with published specifications and free from defects in material and/or workmanship. hitachi, at its option, will replace any emulator products returned intact to the factory, transportation charges prepaid, which hitachi, upon inspection, shall determine to be defective in material and/or workmanship. the foregoing shall constitute the sole remedy for any breach of hitachi's warranty. see the hitachi warranty booklet for details on the warranty period. this warranty extends only to you, the original purchaser. it is not transferable to anyone who subsequently purchases the emulator product from you. hitachi is not liable for any claim made by a third party or made by you for a third party. disclaimer hitachi makes no warranties, either express or implied, oral or written, except as provided herein, including without limitation thereof, warranties as to marketability, merchantability, fitness for any particular purpose or use, or against infringement of any patent. in no event shall hitachi be liable for any direct, incidental or consequential damages of any nature, or losses or expenses resulting from any defective emulator product, the use of any emulator product, or its documentation, even if advised of the possibility of such damages. except as expressly stated otherwise in this warranty, this emulator product is sold "as is ", and you must assume all risk for the use and results obtained from the emulator product.
rev. 2.0, 01/01, page iii of vi state law: some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, so the above limitation or exclusion may not apply to you. this warranty gives you specific legal rights, and you may have other rights which may vary from state to state. the warranty is void in the following cases: hitachi shall have no liability or legal responsibility for any problems caused by misuse, abuse, misapplication, neglect, improper handling, installation, repair or modifications of the emulator product without hitachi's prior written consent or any problems caused by the user system. all rights reserved: this user's manual and emulator product are copyrighted and all rights are reserved by hitachi. no part of this user's manual, all or part, may be reproduced or duplicated in any form, in hard- copy or machine-readable form, by any means available without hitachi's prior written consent. other important things to keep in mind: 1. circuitry and other examples described herein are meant merely to indicate the characteristics and performance of hitachi's semiconductor products. hitachi assumes no responsibility for any intellectual property claims or other problems that may result from applications based on the examples described herein. 2. no license is granted by implication or otherwise under any patents or other rights of any third party or hitachi. figures: some figures in this user's manual may show items different from your actual system. device names: sections 1 to 5 in this user?s manual use shxxxx as an example of the device names. limited anticipation of danger: hitachi cannot anticipate every possible circumstance that might involve a potential hazard. the warnings in this user's manual and on the emulator product are therefore not all inclusive. therefore, you must use the emulator product safely at your own risk.
rev. 2.0, 01/01, page iv of vi safety page read first read this user's manual before using this emulator product. keep the user's manual handy for future reference. do not attempt to use the emulator product until you fully understand its mechanism. definition of signal words this is the safety alert symbol. it is used to alert you to potential personal injury hazards. obey all safety messages that follow this symbol to avoid possible injury or death. danger danger indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury. warning warning indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. caution caution indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury. caution caution used without the safety alert symbol indicates a potentially hazardous situation which, if not avoided, may result in property damage. note emphasizes essential information.
rev. 2.0, 01/01, page v of vi warning observe the precautions listed below. failure to do so will result in a fire hazard and will damage the user system and the emulator product or will result in personal injury. the user program will be lost. 1. do not repair or remodel the emulator product by yourself for electric shock prevention and quality assurance. 2. always switch off the host computer and user system before connecting or disconnecting any cables or parts. 3. connect the connectors in the user system and in the user interface cable by confirming the correct direction. 4. if the pci interface board for the e6000 or e8000 emulator (hs6000eic01h) and the e10a emulator pci card are mounted on the same host computer, the connectors may be illegally connected.
rev. 2.0, 01/01, page vi of vi warnings on emulator usage be sure to read and understand the warnings below before using this emulator. note that these are the main warnings, not the complete list. warning always switch off the host computer and user system before connecting or disconnecting any cables or parts. failure to do so will result in a fire hazard and will damage the user system and the emulator product or will result in personal injury. the user program will be lost. caution place the host computer and user system so that no cable is bent or twisted. a bent or twisted cable will impose stress on the user interface leading to connection or contact failure. make sure that the host computer and the user system are placed in a secure position so that they do not move during use nor impose stress on the user interface.
rev. 2.0, 01/01, page i of x preface thank you for purchasing the e10a emulator. caution read section 2, preparation before use, of this user?s manual before using the emulator product. incorrect operation will damage the user system and the emulator product. this emulator is an efficient development tool for software and hardware of user systems based on hitachi?s original microprocessor. the emulator operates using the hitachi debugging interface (hereafter referred to as the hdi), which is the interface program that runs on microsoft ? windows ? 95, microsoft ? windows ? 98, or microsoft ? windows nt ? operating system. this manual describes the functions and operating procedures of the e10a emulator. sections 1 to 5 describe common features of all types of e10a emulators. section 6 describes supplements to the e10a emulator. read section 1.1, warnings, carefully before using the emulator. this manual consists of six sections. the information contained in each section is summarized below: ? section 1, overview, gives the emulator overview. ? section 2, preparation before use, gives instructions for first-time users, such as preparation before use and system connection. ? section 3, tutorial, describes hdi operating examples. ? section 4, descriptions of windows, describes hdi windows for operating the emulator. ? section 5, command-line functions describes how to input hdi commands and command types. ? section 6, shxxxx e10a emulator specifications describes the features of the e10a emulator for each mcu. section 7 describes the important information of the e10a emulator according to emulator products. read these sections before using the e10a emulator. the hdi installation disks are provided by the cd-r. refer to the descriptions in the manuals of the host computer or operating system.
rev. 2.0, 01/01, page ii of x related manuals: ? sh series cross assembler user's manual ? h series linkage editor user's manual ? h series librarian user's manual ? superh risc engine c/c++ compiler user's manual ? hitachi debugging interface user's manual ? hardware manual for each mcu ? programming manual for each mcu notes: 1. ibm pc is a registered trademark of international business machines corporation. 2. microsoft ? , windows ? , and windows nt ? are registered trademarks of microsoft corporation in the united states and/or other countries. microsoft ? windows ? 95 operating system is referred to as windows ? 95 in this user's manual. microsoft ? windows ? 98 operating system is referred to as windows ? 98 in this user's manual.
rev. 2.0, 01/01, page iii of x contents section 1 overview ...........................................................................................................1 1.1 warnings .................................................................................................................... .......3 1.2 environmental conditions.................................................................................................4 1.3 components.................................................................................................................. .....6 section 2 preparation before use ..................................................................................7 2.1 emulator preparation........................................................................................................ .7 2.2 hdi installation............................................................................................................ .....8 2.2.1 installing under windows ? 95 and windows ? 98 operating systems ...................8 2.2.2 installing under windows nt ? 4.0 operating system ..........................................9 2.2.3 installing under windows ? 2000 operating system .............................................10 2.3 connecting the card emulator to the host computer.......................................................11 2.4 connecting the card emulator to the user system ...........................................................12 2.5 system check ................................................................................................................ ....15 2.6 ending the hdi .............................................................................................................. ...21 2.7 uninstalling the hdi ........................................................................................................ .22 2.8 cd-r ........................................................................................................................ .........23 2.8.1 configuration of the cd-r...................................................................................23 2.9 support ..................................................................................................................... .........23 section 3 tutorial ..............................................................................................................25 3.1 introduction ................................................................................................................ .......25 3.2 running the hdi ............................................................................................................. ..27 3.3 [hdi] window ................................................................................................................ ..28 3.4 setting up the emulator..................................................................................................... 29 3.5 setting the [configuration] dialog box ............................................................................30 3.6 checking the operation of the target memory for downloading ....................................31 3.7 downloading the tutorial program...................................................................................33 3.7.1 downloading the tutorial program......................................................................33 3.7.2 displaying the source program............................................................................34 3.8 setting a software breakpoint...........................................................................................36 3.9 setting registers........................................................................................................... .....37 3.10 executing the program ...................................................................................................... 39 3.11 reviewing breakpoints .....................................................................................................4 1 3.12 viewing memory ............................................................................................................. .42 3.13 watching variables ......................................................................................................... ..43 3.14 stepping through a program.............................................................................................46 3.14.1 executing [step in] command .............................................................................46 3.14.2 executing [step out] command ..........................................................................48
rev. 2.0, 01/01, page iv of x 3.14.3 executing [step over] command ........................................................................50 3.15 forced breaking of program executions...........................................................................52 3.16 displaying local variables ...............................................................................................53 3.17 break function ............................................................................................................. .....54 3.17.1 software break function......................................................................................54 3.18 hardware break function .................................................................................................60 3.18.1 setting the sequential break condition ...............................................................68 3.19 trace functions ............................................................................................................ .....73 3.19.1 internal trace function ........................................................................................75 3.19.2 aud trace function............................................................................................77 3.19.3 vp_map translation ...........................................................................................79 3.20 stack trace function....................................................................................................... ..82 3.21 profiling function ......................................................................................................... ....84 3.22 download function to the flash memory area ................................................................89 3.23 what next?................................................................................................................. .......95 section 4 descriptions of windows .............................................................................97 4.1 hdi windows................................................................................................................. ...97 4.2 descriptions of each window...........................................................................................100 4.2.1 [configuration] dialog box .................................................................................100 4.2.2 [breakpoints] window .........................................................................................108 4.2.3 [break] dialog box ..............................................................................................111 4.2.4 [break point] dialog box.....................................................................................117 4.2.5 [break condition] dialog box .............................................................................119 4.2.6 [break condition] dialog box pages ...................................................................121 4.2.7 [trace] window ...................................................................................................133 4.2.8 [trace acquisition] dialog box ...........................................................................135 4.2.9 [system status] window ......................................................................................138 section 5 command-line functions .............................................................................141 5.1 table and symbol description ..........................................................................................141 5.1.1 format ..................................................................................................................14 1 5.1.2 parameter input ....................................................................................................141 5.1.3 examples ..............................................................................................................142 5.1.4 related items........................................................................................................142 5.2 command descriptions .....................................................................................................143 5.2.1 aud_clock:aucl..........................................................................................145 5.2.2 aud_mode:aum .............................................................................................147 5.2.3 aud_trace:aut.............................................................................................149 5.2.4 breakcondition_clear: bcc .................................................................151 5.2.5 breakcondition_display: bcd .............................................................152 5.2.6 breakcondition_enable: bce...............................................................153 5.2.7 breakcondition_set: bcs........................................................................154
rev. 2.0, 01/01, page v of x 5.2.8 breakpoint: bp..............................................................................................158 5.2.9 breakpoint_clear: bc ..............................................................................160 5.2.10 breakpoint_display: bd ..........................................................................162 5.2.11 breakpoint_enable: be............................................................................163 5.2.12 device_type: de............................................................................................165 5.2.13 go_option: gp ................................................................................................166 5.2.14 jtag_clock: jck ...........................................................................................168 5.2.15 memoryarea_set: mas .............................................................................170 5.2.16 refresh: rf .....................................................................................................172 5.2.17 restart: rst...................................................................................................173 5.2.18 status: sts......................................................................................................174 5.2.19 step_interrupt: si .......................................................................................175 5.2.20 trace_display: td.......................................................................................176 5.2.21 ubc_mode:um ................................................................................................178 5.2.22 vpmap_clear: vc .........................................................................................179 5.2.23 vpmap_display: vd .....................................................................................180 5.2.24 vpmap_enable: ve .......................................................................................181 5.2.25 vpmap_set: vs................................................................................................182 section 6 sh7750 e10a emulator specifications ...................................................183 6.1 components of the emulator.............................................................................................183 6.2 pin arrangement of the hitachi-udi port connector .......................................................184 6.3 user system interface circuit ...........................................................................................186 6.4 differences between the sh7750 and sh7750s and the emulator...................................188 6.5 specific functions for the sh7750 e10a emulator..........................................................191 6.5.1 emulator driver selection....................................................................................191 6.5.2 break condition functions...................................................................................192 6.5.3 notes on setting the [breakpoint] dialog box.....................................................194 6.5.4 notes on using the jtag clock (tck) ..............................................................196 6.5.5 trace functions ....................................................................................................196 6.5.6 notes on using the profile function ....................................................................200 6.5.7 sh7750 e10a emulator useful functions ..........................................................202 6.5.8 notes on hdi .......................................................................................................206
rev. 2.0, 01/01, page vi of x figures figure 1.1 system configuration with the emulator (pcmcia card emulator used) ...........1 figure 1.2 system configuration with the emulator (pci card emulator used) ....................2 figure 2.1 emulator preparation flow chart ...........................................................................7 figure 2.2 inserting the pcmcia card emulator in the host computer?s slot......................11 figure 2.3 inserting the pci card emulator in the host computer?s slot...............................11 figure 2.4 connecting the user system interface cable to the user system when the 14-pin straight type connector is used .................................................13 figure 2.5 user system example.............................................................................................14 figure 2.6 [start] menu......................................................................................................... ...15 figure 2.7 [select session] dialog box ...................................................................................16 figure 2.8 [e10a driver details] dialog box .........................................................................17 figure 2.9 dialog box of the reset signal input request message .....................................18 figure 2.10 [hdi] status bar .................................................................................................... .18 figure 2.11 [jtag connector disconnected] dialog box ........................................................18 figure 2.12 [can not find /reset signal] dialog box .............................................................19 figure 2.13 [check the connection] dialog box........................................................................19 figure 2.14 [communication timeout error] dialog box ......................................19 figure 2.15 [invalid aseram firmware!] dialog box ................................................20 figure 2.16 [error jtag boot] dialog box...............................................................................20 figure 2.17 [unable to restore the previous driver settings] dialog box...................................20 figure 2.18 [exit hdi] dialog box ...........................................................................................21 figure 2.19 [save session] dialog box......................................................................................21 figure 3.1 [start] menu......................................................................................................... ...27 figure 3.2 [hdi] window........................................................................................................2 8 figure 3.3 [configuration] dialog box....................................................................................30 figure 3.4 [open memory window] dialog box ....................................................................31 figure 3.5 [memory] window .................................................................................................31 figure 3.6 [load program] dialog box ...................................................................................33 figure 3.7 [hdi] dialog box...................................................................................................33 figure 3.8 [open] dialog box .................................................................................................34 figure 3.9 [source] window (displaying the source program) ..............................................35 figure 3.10 [source] window (setting a software breakpoint) ................................................36 figure 3.11 [registers] window ................................................................................................37 figure 3.12 [register] dialog box (pc) ....................................................................................38 figure 3.13 [go] button......................................................................................................... ....39 figure 3.14 [source] window (break status)............................................................................39 figure 3.15 [system status] window ........................................................................................40 figure 3.16 [breakpoints] window............................................................................................41 figure 3.17 [open memory window] dialog box ....................................................................42 figure 3.18 [memory] window .................................................................................................42 figure 3.19 [instant watch] dialog box....................................................................................43
rev. 2.0, 01/01, page vii of x figure 3.20 [watch] window (displaying the array) ...............................................................44 figure 3.21 [add watch] dialog box........................................................................................44 figure 3.22 [watch] window (displaying the variable)...........................................................45 figure 3.23 [watch] window (displaying array elements) .....................................................45 figure 3.24 [step in] button .................................................................................................... ..46 figure 3.25 [source] window (step in).....................................................................................47 figure 3.26 [step out] button................................................................................................... .48 figure 3.27 [hdi] window (step out) ......................................................................................48 figure 3.28 [hdi] window (step in ?> step in) .......................................................................49 figure 3.29 [source] window (before step over execution) ...................................................50 figure 3.30 [step over] button.................................................................................................. 50 figure 3.31 [hdi] window (step over) ....................................................................................51 figure 3.32 [go] button......................................................................................................... ....52 figure 3.33 [stop] button ....................................................................................................... ...52 figure 3.34 [locals] window ....................................................................................................5 3 figure 3.35 [breakpoints] window (before software breakpoint setting)...............................54 figure 3.36 [point] page ([break] dialog box) .........................................................................55 figure 3.37 [break point] dialog box .......................................................................................56 figure 3.38 [point] page ([break] dialog box) (after software breakpoint setting)...............57 figure 3.39 [breakpoints] window (software breakpoint setting)...........................................58 figure 3.40 [source] window at execution stop (software break) ..........................................58 figure 3.41 displayed contents of the [system status] window (software break)..................59 figure 3.42 [breakpoints] window (before hardware break condition setting).....................60 figure 3.43 [condition] page ([break] dialog box)..................................................................61 figure 3.44 [address] page ([break condition 1] dialog box).................................................62 figure 3.45 [bus state] page ([break condition 1] dialog box)...............................................63 figure 3.46 [break] dialog box (after hardware break condition setting) ............................64 figure 3.47 [breakpoints] window ([break condition 1] setting)............................................65 figure 3.48 [source] window at execution stop (break condition 1)......................................66 figure 3.49 displayed contents of the [system status] window (break condition 1) .............67 figure 3.50 [configuration] dialog box (sequential break setting).........................................69 figure 3.51 [breakpoints] window (after sequential break condition setting) ......................70 figure 3.52 [source] window at execution stop (sequential break)........................................71 figure 3.53 displayed contents of the [system status] window (sequential break) ...............72 figure 3.54 [trace mode] window............................................................................................75 figure 3.55 [trace] window...................................................................................................... 76 figure 3.56 [trace mode] window............................................................................................77 figure 3.57 [trace] window in the sh7751 e10a emulator....................................................78 figure 3.58 address translation according to vp_map tables ...............................................80 figure 3.59 [source] window (software breakpoint setting)...................................................82 figure 3.60 [stack trace] window............................................................................................83 figure 3.61 [profile-list] window ............................................................................................84 figure 3.62 selection of [enable profiler] .................................................................................85
rev. 2.0, 01/01, page viii of x figure 3.63 [select data] dialog box........................................................................................86 figure 3.64 [source] window (software break setting) ...........................................................87 figure 3.65 [profile-list] window ............................................................................................87 figure 3.66 [profile-tree] window ...........................................................................................88 figure 3.67 [profile-chart] window..........................................................................................88 figure 3.68 [loading flash memory] page ................................................................................90 figure 3.69 flash memory wiring.............................................................................................92 figure 3.70 [loading flash memory] page ................................................................................93 figure 4.1 [configuration] dialog box....................................................................................100 figure 4.2 [general] page ([configuration] dialog box) ........................................................102 figure 4.3 warning message box............................................................................................104 figure 4.4 [e10a driver details] dialog box .........................................................................105 figure 4.5 [loading flash memory] page ([configuration] dialog box).................................106 figure 4.6 [breakpoints] window............................................................................................108 figure 4.7 [break] dialog box ................................................................................................111 figure 4.8 [point] page ([break] dialog box) .........................................................................113 figure 4.9 [condition] page ([break] dialog box)..................................................................115 figure 4.10 [break point] dialog box .......................................................................................117 figure 4.11 [break condition] dialog box................................................................................119 figure 4.12 [address] page ([break condition 1] dialog box).................................................123 figure 4.13 [data] page ([break condition 1] dialog box) ......................................................125 figure 4.14 [asid] page ([break condition] dialog box) .......................................................127 figure 4.15 [bus state] page ([break condition] dialog box)..................................................128 figure 4.16 [count] page ([break condition] dialog box).......................................................130 figure 4.17 [general] page ([break condition] dialog box) ....................................................131 figure 4.18 [trace] window...................................................................................................... 133 figure 4.19 [trace mode] page ([trace acquisition] dialog box)............................................136 figure 4.20 [system status] window ........................................................................................138 figure 5.1 tlb error message dialog ....................................................................................176 figure 6.1 pin arrangement of the hitachi-udi port connector (14 pins) .............................184 figure 6.2 user system interface circuit (hs7750kcm01h) (model name: hs0005kcm03h)..........................................................................186 figure 6.3 user system interface circuit (hs7750kci01h) (model name: hs0005kci03h)............................................................................187 figure 6.4 message box for clearing a tlb-error .................................................................196 figure 6.5 message box for clearing a tlb error..................................................................198 figure 6.6 message box for clearing a tlb error..................................................................199
rev. 2.0, 01/01, page ix of x tables table 1.1 environmental conditions ......................................................................................4 table 1.2 operating environments.........................................................................................5 table 2.1 recommended hitachi-udi port connector ..........................................................12 table 2.2 contents of the cd-r directories...........................................................................23 table 3.1 tutorial program: configuration and parts.............................................................25 table 3.2 step option ........................................................................................................... ..46 table 3.3 sequential break conditions ..................................................................................68 table 3.4 aud trace functions.............................................................................................74 table 3.5 address translation tables ....................................................................................81 table 3.6 module interface.....................................................................................................8 9 table 3.7 [loading flash memory] page options ...................................................................91 table 3.8 example of board specifications ...........................................................................92 table 3.9 sample program specifications ..............................................................................93 table 4.1 hdi window menus and related manual entries .................................................97 table 4.2 [configuration] dialog box page ...........................................................................101 table 4.3 [general] page options...........................................................................................103 table 4.4 options for the [e10a driver details] dialog box ................................................105 table 4.5 [loading flash memory] page options ...................................................................107 table 4.6 [breakpoints] window display items ....................................................................109 table 4.7 [breakpoints] window pop-up menu operation ....................................................110 table 4.8 [break] dialog box pages ......................................................................................112 table 4.9 [point] page options...............................................................................................114 table 4.10 [condition] page options .......................................................................................116 table 4.11 [address] page options ..........................................................................................118 table 4.12 setting conditions in [break condition] dialog boxes..........................................121 table 4.13 [break condition] dialog box pages .....................................................................122 table 4.14 [address] page options ..........................................................................................124 table 4.15 address options .....................................................................................................1 24 table 4.16 [data] page options................................................................................................12 6 table 4.17 [asid] page options..............................................................................................127 table 4.18 [bus state] page options ........................................................................................129 table 4.19 [count] page options .............................................................................................130 table 4.20 [general] page options...........................................................................................132 table 4.21 [trace] window display items...............................................................................134 table 4.22 [trace acquisition] dialog box page options .......................................................135 table 4.23 [trace mode] page options ....................................................................................137 table 4.24 [system status] window display items .................................................................139 table 5.1 e10a hdi commands............................................................................................143 table 5.2 aud_clock command parameter .....................................................................145 table 5.3 aud_mode command parameter .......................................................................147 table 5.4 aud_trace command parameter......................................................................149
rev. 2.0, 01/01, page x of x table 5.5 breakcondition_clear command parameter...........................................151 table 5.6 breakcondition_display command parameter .......................................152 table 5.7 breakcondition_enable command parameters.......................................153 table 5.8 breakcondition_set command parameters ...............................................155 table 5.9 breakpoint command parameters...................................................................158 table 5.10 breakpoint_clear command parameters....................................................160 table 5.11 breakpoint_display command parameter..................................................162 table 5.12 breakpoint_enable command parameters .................................................163 table 5.13 device_type command parameter ...................................................................165 table 5.14 go_option command parameter .......................................................................166 table 5.15 jtag_clock command parameter ....................................................................168 table 5.16 memoryarea_set command parameters ......................................................170 table 5.17 refresh command parameter ............................................................................172 table 5.18 restart command parameter............................................................................173 table 5.19 status command parameter ..............................................................................174 table 5.20 step_interrupt command parameter ............................................................175 table 5.21 trace_display command parameter..............................................................176 table 5.22 ubc_mode command parameter........................................................................178 table 5.23 vpmap_clear command parameter.................................................................179 table 5.24 vpmap_display command parameter .............................................................180 table 5.25 vpmap_enable command parameter ..............................................................181 table 5.26 vpmap_set command parameters .....................................................................182 table 6.1 components of the emulator (hs7750kcm01h or hs7750kci01h)..................183 table 6.2 register initial values at emulator power-on .......................................................188 table 6.3 type number and driver........................................................................................191 table 6.4 types of break conditions .....................................................................................192 table 6.5 dialog boxes for setting the break condition .......................................................193 table 6.6 sequential break conditions ..................................................................................194 table 6.7 type number and aud function ..........................................................................196 table 6.8 trace functions ......................................................................................................1 97 table 6.9 measurement events...............................................................................................203 table 6.10 performance count conditions...............................................................................204 table 6.11 watchdog timer register.......................................................................................210
rev. 2.0, 01/01, page 1 of 214 section 1 overview the e10a emulator (hereafter referred to as the emulator) is a software and hardware development support tool for application systems using the microprocessor developed by hitachi, ltd. the pcmcia card emulator or pci card emulator (hereafter referred to as the card emulator), which is the main unit of the emulator, is connected, through the hitachi-udi (user debug interface) port*, to the user system. the user system can be debugged under the conditions similar to the actual application conditions. the emulator enables debugging anywhere indoors or out. the host computer for controlling the emulator must be an ibm pc compatible machine with a pcmcia type ii or pci slot. figures 1.1 and 1.2 show the system configuration using the emulator. note: the hitachi-udi is an interface compatible with the joint test action group (jtag) specifications. insert pc card emulator h-udi micro computer development system hitachi pc card user system interface cable host computer (pc with pcmcia type ii slot) pcmcia card emulator insert into the pcmcia type ii slot shxxxx user system connect to the hitachi-udi port connector figure 1.1 system configuration with the emulator (pcmcia card emulator used)
rev. 2.0, 01/01, page 2 of 214 user system host computer user system interface cable pci card emulator shxxxx insert into the pci slot figure 1.2 system configuration with the emulator (pci card emulator used) the emulator provides the following features: ? excellent cost-performance card emulator compactness and low price are implemented using the pcmcia interface or the pci interface. ? realtime emulation realtime emulation of the user system is enabled at the maximum operating frequency of the cpu. ? excellent operability using the hitachi debugging interface (hdi) on the microsoft ? windows ? 95, microsoft ? windows ? 98, microsoft ? windows ? 2000, and microsoft ? windows nt ? operating systems enables user program debugging using a pointing device such as a mouse. the hdi enables high-speed downloading of load module files. ? various debugging functions various break and trace functions enable efficient debugging. breakpoints and break conditions can be set by the specific window, trace information can be displayed on a window, and command-line functions can be used. ? memory access during emulation during emulation, the memory contents can be read and modified. ? debugging of the user system in the final development stage the user system can be debugged under conditions similar to the actual application conditions. ? compact debugging environment when the card emulator specific to the pcmcia interface is used, a laptop computer can be used as a host computer, creating a debugging environment in any place. ? aud trace function* the aud trace function enables realtime trace.
rev. 2.0, 01/01, page 3 of 214 note: the aud is an abbreviation of the advanced user debugger. support for the aud varies with the product. 1.1 warnings caution read the following warnings before using the emulator product. incorrect operation will damage the user system and the emulator product. the user program will be lost. 1. check all components against the component list after unpacking the emulator. 2. never place heavy objects on the casing. 3. protect the emulator from excessive impacts and stresses. for details, refer to section 1.2, environmental conditions. 4. do not insert the emulator into any slot (pcmcia type ii slot or pci slot) other than the specified one. 5. when moving the host computer or user system, take care not to vibrate or damage it. 6. after connecting the cable, check that it is connected correctly. for details, refer to section 2, preparation before use. 7. supply power to the connected equipment after connecting all cables. cables must not be connected or removed while the power is on.
rev. 2.0, 01/01, page 4 of 214 1.2 environmental conditions caution observe the conditions listed in tables 1.1 and 1.2 when using the emulator. failure to do so will cause illegal operation in the user system, the emulator product, and the user program. table 1.1 environmental conditions item specifications temperature operating: +10c to +35c storage: ?10c to +50c humidity operating: 35% rh to 80% rh, no condensation storage: 35% rh to 80% rh, no condensation vibration operating: 2.45 m/s 2 max. storage: 4.9 m/s 2 max. transportation: 14.7 m/s 2 max. ambient gases no corrosive gases may be present table 1.2 lists the acceptable operating environments.
rev. 2.0, 01/01, page 5 of 214 table 1.2 operating environments item description host computer built-in pentium or higher-performance cpu (200 mhz or higher recommended); ibm pc or compatible machine with the pcmcia type ii slot or the pci slot. os windows ? 95, windows ? 98, windows ? 2000, or windows nt ? minimum memory capacity 32 mbytes or more (double of the load module size recommended) hard-disk capacity installation disk capacity: 10 mbytes or more. (prepare an area at least double the memory capacity (four-times or more recommended) as the swap area.) pointing device such as mouse connectable to the host computer; compatible with windows ? 95, windows ? 98, windows ? 2000, and windows nt ? . power voltage 5.0 0.25 v current consumption hsxxxxkcm01h: 110 ma (max) hsxxxxkcm02h: 230 ma (max) hsxxxxkci01h: 340 ma (max) hsxxxxkci02h: 600 ma (max) cd-rom drive required to install the hdi for the emulator or refer to the emulator user?s manual.
rev. 2.0, 01/01, page 6 of 214 1.3 components check all the components unpacking. for details on the e10a emulator components, refer to section 6.1, components of the emulator. if the components are not complete, contact a hitachi sales agency.
rev. 2.0, 01/01, page 7 of 214 section 2 preparation before use 2.1 emulator preparation warning read the reference sections shaded in figure 2.1 before using the emulator product. incorrect operation will damage the user system and the emulator product. the user program will be lost. unpack the emulator and prepare it for use as follows: section 2 section 3 input the user system reset signal unpack the emulator check the components against the component list start the hdi turn on the user system component list when the emulator is used first. when the emulator is used for second time or later. reference set up the emulator - install the hdi - insert the card emulator figure 2.1 emulator preparation flow chart
rev. 2.0, 01/01, page 8 of 214 2.2 hdi installation when the cd-r is inserted in the host computer?s cd-rom drive, the hdi installation wizard is automatically activated (holding the shift key down while the cd-r is inserted cancels this automatic activation). to run the installation wizard when it has not been automatically activated, execute setup.exe from the root directory of the cd-r. follow the cues given by the installation wizard to install the hdi. since hardware settings are also made during installation, the installation procedure differs according to the operating system or interface (pci or pcmcia) being used. follow the installation steps carefully according to the environment you are using. 2.2.1 installing under windows ? 95 and windows ? 98 operating systems (1) when the emulator is a pci card: 1. install the hdi (when the component type has to be selected during installation, be sure to select [pci card driver]). 2. shut the operating system down and turn off the power to the host computer. 3. insert the pci-card emulator in a slot on the host computer. refer to section 2.3, connecting the card emulator to the host computer. 4. restart the host computer. the hardware is now recognized and the driver is automatically installed.* (2) when the emulator is a pcmcia card: 1. install the hdi (when the component type has to be selected during installation, be sure to select [pc card driver (pcmcia)]). 2. insert the pcmcia-card emulator in the host computer?s slot. refer to section 2.3, connecting the card emulator to the host computer. 3. the hardware is now recognized and the driver is automatically installed.* note: when [add new hardware wizard] is displayed, select the [search for the best driver for your device. (recommended)] radio button and then the [specify a location] check box to select the path to be searched for drivers. the location must be specified according to the emulator type, as indicated below: when using the pci-card emulator: :\drivers\pci\95 when using the pcmcia-card emulator: :\drivers\pcmcia\95 ( is the cd-rom drive name.)
rev. 2.0, 01/01, page 9 of 214 2.2.2 installing under windows nt ? 4.0 operating system (1) when the emulator is a pci card: 1. shut the operating system down and turn off the power to the host computer. 2. insert the pci-card emulator in a slot on the host computer. refer to section 2.3, connecting the card emulator to the host computer. 3. start the host computer and log-on with an administrator-level user name. 4. install the hdi. (for a component, be sure to select [pci card driver]. there is a check box for selecting the type name of the product under the [pci card driver] component. select the appropriate type name. if the correct name is not selected, the correct driver will not be installed, and the emulator will not operate.) 5. restart the host computer. (2) when the emulator is a pcmcia card: 1. shut the operating system down and turn off the power to the host computer. 2. insert the pcmcia-card emulator in the host computer?s slot. refer to section 2.3, connecting the card emulator to the host computer. 3. start the host computer and log-on with an administrator-level user name. 4. during hdi installation, the setting value should be checked beforehand because inquiries are made about the resource used by the pcmcia-card emulator. start the [start] menu -> [programs] -> [administrative tools (common)] -> [windows nt diagnostics], check the status of the irq, i/o port, and memory from the resource panel, and determine the setting values that do not conflict with other devices. (the following resources are used: irq: one channel, i/o port: h?f byte, and memory: h?4000 byte.) 5. install the hdi. (for a component, be sure to select [pc card driver (pcmcia)]. there is a check box for selecting the type name of each product under the [pc card driver (pcmcia)] component. select the appropriate type name. if the correct name is not selected, the correct driver will not be installed and the emulator will not operate.) 6. restart the host computer. notes: 1. for the sh7729, sh7729r, and sh7622 e10a emulators, there is a check box for selecting the model name that appears on the component list. select the correct type name. 2. the driver that has been selected in the [drivers] component starts after the host computer is initiated. if the host computer is initiated with the card disconnected or with the incorrect driver installed, the driver cannot initiate and the service control manager informs the system of an error. this, however, is not a problem.
rev. 2.0, 01/01, page 10 of 214 2.2.3 installing under windows ? 2000 operating system (1) when the emulator is a pci card: 1. log-on with an administrator-level user name. 2. install the hdi. (when a component is selected, be sure to select [pci card driver].) 3. shut the operating system down and turn off the power to the host computer. 4. insert the pci-card emulator in a slot on the host computer. refer to section 2.3, connecting the card emulator to the host computer. 5. restart the host computer and log-on with an administrator-level user name. the hardware is now recognized and the driver is automatically installed.* (2) when the emulator is a pcmcia card: 1. log-on with an administrator-level user name. 2. install the hdi. (when a component is selected, be sure to select [pc card driver (pcmcia)].) 3. insert the pcmcia-card emulator in the host computer?s slot. refer to section 2.3, connecting the card emulator to the host computer. 4. the hardware is now recognized and the driver is automatically installed.* note: when [found new hardware wizard] is displayed, select the [search for a suitable driver for my device (recommended).] radio button and then the [specify a location] check box to select the path to be searched for drivers. the location must be specified according to the emulator type, as indicated below: when using the pci-card emulator: :\drivers\pci\2000 when using the pcmcia-card emulator: :\drivers\pcmcia\2000 ( is the cd-rom drive name.)
rev. 2.0, 01/01, page 11 of 214 2.3 connecting the card emulator to the host computer insert the card emulator, according to its type, in a pcmcia type ii slot or pci slot on the host computer (figures 2.2 and 2.3). note: when using windows ? 95, windows ? 98, or windows ? 2000, be sure to install the hdi before putting the card emulator in place. host computer (pc with the pcmcia type ii slot) pcmcia card emulator insert into the pcmcia type ii slot insert pc card emulator h-udi micro computer development system hitachi pc card figure 2.2 inserting the pcmcia card emulator in the host computer?s slot host computer pci card emulator insert into the pci slot figure 2.3 inserting the pci card emulator in the host computer?s slot use the procedure, described in section 2.4, to connect the emulator to the user system with the user system interface cable, or to disconnect them when moving the emulator or the user system.
rev. 2.0, 01/01, page 12 of 214 warning when inserting the pci-card emulator, note the following. failure to do so will damage the host computer. 1. turn off the host computer. 2. insert the emulator into the pci slot in parallel. 3. screw in the emulator after checking the connector and cable positions. 2.4 connecting the card emulator to the user system (1) the hitachi-udi port connector must be installed to the user system. table 2.1 shows the recommended hitachi-udi port connector for the emulator. table 2.1 recommended hitachi-udi port connector connector type number manufacturer specifications 14-pin connector 2514-6002 minnesota mining & manufacturing ltd. 14-pin straight type dx10m-36s screw type 36-pin connector dx10m-36se, dx10gm-36se hirose electric co., ltd. lock-pin type note: when the 14-pin connector is used, do not install any components within 3 mm of the hitachi-udi port connector. when the 36-pin connector is used, do not connect other signal lines to the hitachi- udi port connector. (2) note that the tdo signal of the user system interface cable connector must be connected to the tdi pin of the hitachi-udi port connector and the tdi signal of the user system interface cable connector must be connected to the tdo pin of the hitachi-udi port connector. section 6.2 shows the pin arrangement of the hitachi-udi port connector. (3) figure 2.4 shows how to connect the user system interface cable to the user system when the 14-pin straight type connector is used. connect the ground line of the cable to the user system ground. the end of the ground line has a hole having a diameter of 3 mm, and therefore, when the ground line is screwed to the user system, the screw diameter must be 3 mm.
rev. 2.0, 01/01, page 13 of 214 user system interface cable hitachi-udi port connector user system gnd connection user system gnd line tab pin 1 pin 8 figure 2.4 connecting the user system interface cable to the user system when the 14-pin straight type connector is used notes: 1. to connect the signals output from the hitachi-udi port connector, refer to the device pin alignment. 2. to remove the user system interface cable from the user system, pull the tab on the connector upward. 3. the range of frequencies that the hitachi-udi operates at is different according to the devices used. for details, refer to section 6.5.4, notes on using the jtag clock (tck) and aud clock (audck). 4. connect the hitachi-udi signals from the hitachi-udi port connector directly to the device. 5. when developing user systems, do not connect the tdi and tdo signals of the device to the boundary scan loop, or separate them by using a switch (figure 2.5).
rev. 2.0, 01/01, page 14 of 214 shxxxx hitachi-udi tdi tdo tdi tdo tdi tdo hitachi-udi port jtag port boundary scan loop user system tdi: test data input tdo: test data output tap: test access port ic tap ic tap ic tap tdi tdo figure 2.5 user system example
rev. 2.0, 01/01, page 15 of 214 2.5 system check when the hdi program is executed, use the procedure below to check that the emulator is operating correctly. 1. check that the emulator card is inserted in the host computer?s slot. 2. connect the user system interface cable to the connector of the card emulator. 3. connect the user system interface cable to the hitachi-udi port connector. 4. supply power to the host computer and select [hdi for e10a shxxxx] -> [hitachi debugging interface] from the [start] menu. figure 2.6 [start] menu
rev. 2.0, 01/01, page 16 of 214 5. select the setting to be used. figure 2.7 [select session] dialog box
rev. 2.0, 01/01, page 17 of 214 6. the [e10a driver details] dialog box is displayed. with the [driver] combo box, select the driver to connect the hdi with the emulator. [interface] displays the interface name of the pc interface board to be connected, and [channel] displays the interface to which the board is connected. once the driver is selected in the [e10a driver details] dialog box, this dialog box is not displayed when the hdi is run next time. (this procedure will not be executed by target devices.) figure 2.8 [e10a driver details] dialog box ? with the [driver] combo box, select the driver to connect the hdi with the emulator. ? [interface] displays the interface name of the card emulator to be connected, and [channel] displays the interface to which the board is connected. [driver] combo box: select [e10a pc card driver] to use the pcmcia card emulator. select [e10a pci card driver] to use the pci card emulator. for details, refer to table 6.3 in section 6.5.1, emulator driver selection. [interface] combo box: select [pc card] to use the pcmcia card emulator. [pci] is displayed to use the pci card emulator. (if the driver is not installed, the [pc card] or [pci] is not displayed.) ? click the [close] button.
rev. 2.0, 01/01, page 18 of 214 7. the hdi window is displayed, and the dialog box is displayed as shown in figure 2.9. figure 2.9 dialog box of the reset signal input request message 8. power on the user system. 9. input the reset signal from the user system, and click the [ok] button. 10. when "link up" is displayed on the status bar, the hdi initiation is completed. figure 2.10 [hdi] status bar notes: 1. when the hdi is not linked up even if the above procedure has been executed, the driver will not be set correctly. install drivers provided under the /drivers directory in the cd-r according to the screen instructions. for instructions on how to check the driver has been correctly set, refer to the os manual for your host computer or the following url: http://www.hitachi.co.jp/sicd/english/products/micom/dev_env/tool/eml/e10a/ she10aqa.htm 2. if the user system interface cable is disconnected to the hitachi-udi port connector on the user system during user program execution, the following dialog box will be displayed. figure 2.11 [jtag connector disconnected] dialog box
rev. 2.0, 01/01, page 19 of 214 3. if the emulator is not initiated, the following dialog boxes shown in figures 2.12 through 2.16 will be displayed. (a) if the following dialog box is displayed, the power of the user system may not be input or the reset signal may not be input to the device. check the input circuits for the power of the user system and the reset pin. figure 2.12 [can not find /reset signal] dialog box (b) if the following dialog box is displayed, check that the hitachi-udi port connector on the user system is correctly connected. figure 2.13 [check the connection] dialog box (c) if the following dialog box is displayed, the device may not correctly operate. check if there are reasons for illegal device operation. figure 2.14 [communication timeout error] dialog box
rev. 2.0, 01/01, page 20 of 214 figure 2.15 [invalid aseram firmware!] dialog box figure 2.16 [error jtag boot] dialog box 4. if the driver is not correctly connected, the following dialog box will be displayed. figure 2.17 [unable to restore the previous driver settings] dialog box the [e10a driver details] dialog box is displayed when the [ok] button is clicked. select the correct driver. for details, refer to section 6.5.1, emulator driver selection.
rev. 2.0, 01/01, page 21 of 214 2.6 ending the hdi exit the hdi by using the following procedure: 1. select [exit] from the [file] menu to end the hdi. when the [exit hdi] dialog box is displayed, click the [yes] button. figure 2.18 [exit hdi] dialog box 2. then, the [save session] dialog box is displayed. if necessary, click the [yes] button to save session. after saving session, the hdi ends. if not necessary, click the [no] button to end the hdi. figure 2.19 [save session] dialog box 3. turn the user system off.
rev. 2.0, 01/01, page 22 of 214 2.7 uninstalling the hdi follow this procedure to remove the installed hdi from the user?s host computer. 1. open [add/remove programs properties] from the control panel. select the hdi program from the list and click the [add/remove?] button. 2. the setup program is executed again and the installed application can be changed, modified, or removed. when the application is to be uninstalled, select removal. caution a shared file may be detected while the program is being removed. if another hdi may be using the shared file, do not remove the file. when microsoft ? windows nt ? 4.0 operating system is used, the removal of the registry information on the driver may be asked. if other hdi may use the target driver, do not remove the registry information. if another hdi does not start up after the removal process, re-install that hdi.
rev. 2.0, 01/01, page 23 of 214 2.8 cd-r 2.8.1 configuration of the cd-r the root directory of the cd-r contains a setup program for hdi installation. the folders contain the files and programs listed below. table 2.2 contents of the cd-r directories directory name contents description dlls microsoft ? runtime library a runtime library for the hdi. the version is checked at installation and this library is copied to the hard disk as part of the installation process. drivers e10a emulator driver the e10a emulator drivers. help online help for the e10a emulator an online help file. this is copied to the hard disk as part of the installation process. manual e10a emulator manual precautions on using the e10a emulator and the user?s manual. these are provided as pdf files. pdf_read adobe ? acrobat ? reader setup program adobe ? acrobat ? reader is an application for displaying, viewing, and printing pdf files. 2.9 support information on the latest version of the hdi and other supporting information for the emulator can be found on the web site. access the following url: http://www.hitachi.co.jp/sicd/english/products/micom/dev_env/tool/eml/e10a/e10atop.htm
rev. 2.0, 01/01, page 24 of 214
rev. 2.0, 01/01, page 25 of 214 section 3 tutorial 3.1 introduction the following describes the main functions of the hdi by using a tutorial program. the tutorial program is based on the c program that sorts ten random data items in ascending or descending order. the tutorial program performs the following actions: ? the main function generates random data to be sorted. ? the sort function sorts the generated random data in ascending order. ? the change function then sorts the data in descending order. the file tutorial.c contains source code for the tutorial program. the file tutorial.abs is a compiled load module in the dwarf2 format. table 3.1 is a list of the parts of the tutorial program and an outline of their configuration on the hard disk. table 3.1 tutorial program: configuration and parts item contents workspace for hew v1.2 [installation directory]\tutorial\tutorial.hws load module [installation directory]\tutorial\tutorial\debug\tutorial.abs main program (source file) [installation directory]\tutorial\tutorial\tutorial.c stack information file [installation directory]\tutorial\tutorial\debug\tutorial.sni use area 3 (cs3 space) as the operating environment. the mmu function is not used.
rev. 2.0, 01/01, page 26 of 214 notes: 1. operation of tutorial.abs is big endian. for little-endian operation, tutorial.abs must be recompiled. after recompilation, the addresses may differ from those given in this section. 2. this program was created by using hitachi embedded workshop (hereafter referred to as hew) v1.2. older versions of hew will not open the workspace included with the package, so create a new workspace in such situations. 3. this program was compiled without optimization for the sh2 cpu. if recompiled with different settings, the addresses may differ from those given in this section. 4. tutorial.abs is a load module in the dwarf2 format. if a load module is recreated in the sysrof format, the amount of information displayed on the hdi screen during the program?s execution will be reduced. 5. this section describes general usage examples for the emulator. for the specifications of particular products, refer to section 6 or the online help file.
rev. 2.0, 01/01, page 27 of 214 3.2 running the hdi to run the hdi, select the [hdi for e10a shxxxx] -> [hitachi debugging interface] from the [start] menu. figure 3.1 [start] menu for the procedure of running the hdi, refer to section 2.5, system check.
rev. 2.0, 01/01, page 28 of 214 3.3 [hdi] window figure 3.2 [hdi] window the key functions of the hdi are described in section 4, descriptions of windows. numbers in figure 3.2 indicate the following: 1. menu bar: gives the user access to the hdi commands for using the hdi debugger. 2. toolbar: provides convenient buttons as shortcuts for the most frequently used menu commands. 3. source window: displays the source program being debugged. 4. status bar: displays the status of the emulator, and progress information about downloading. 5. [help] button: activates online help about any features of the hdi user interface.
rev. 2.0, 01/01, page 29 of 214 3.4 setting up the emulator the clocks which are used for data communications must be set up on the emulator before the program is downloaded. ? aud clock a clock used in acquiring aud traces. if its frequency is set too low, complete data may not be acquired during realtime tracing. if the frequency is set too high, the upper limit for the device?s aud clock may be exceeded. the aud clock is only needed for emulators that have an aud trace function. ? jtag clock (tck) a communication clock for downloading data to the emulator except for acquiring aud trace. if its frequency is set too low, the speed of downloading will be lowered. if its frequency is set too high, the upper limit for the device?s tck clock may be exceeded. for details of the limitations on both clocks, refer to section 6.5.4, notes on using the jtag clock (tck) and aud clock (audck). the following is a description of the procedure used to set the clocks.
rev. 2.0, 01/01, page 30 of 214 3.5 setting the [configuration] dialog box ? select [configure platform...] from the [setup] menu to set a communication clock. the [configuration] dialog box is displayed. figure 3.3 [configuration] dialog box ? set any value in the [aud clock] and [jtag clock] combo boxes. the clock also operates with the default value. note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help. ? click the [ok] button to set a configuration.
rev. 2.0, 01/01, page 31 of 214 3.6 checking the operation of the target memory for downloading check that the destination memory area for downloading is operating correctly. when the destination memory is sdram or dram, a register in the bus controller must be set before downloading. set the bus controller correctly in the [i/o registers] window according to the memory type. for details, refer to section 8.6, i/o register display, in the hitachi debugging interface user?s manual. when the required settings, such as the settings for the bus controller, have been completed, display and edit the contents of the destination memory in the [memory] window to check that the memory is operating correctly. note: the above way of checking the operation of memory may be inadequate. it is recommended that a program for checking the memory be created. ? select [memory?] from the [view] menu, enter h?0c000000 in the [address] edit box, and set the format in the [format] combo box to byte . figure 3.4 [open memory window] dialog box ? click the [ok] button. the [memory] window is displayed and shows the specified memory area. figure 3.5 [memory] window
rev. 2.0, 01/01, page 32 of 214 ? placing the mouse cursor on a point in the display of data in the [memory] window and double clicking allows the values at that point to be changed. data can also be directly edited around the current position of the text cursor.
rev. 2.0, 01/01, page 33 of 214 3.7 downloading the tutorial program 3.7.1 downloading the tutorial program download the object program to be debugged. ? select [load program...] from the [file] menu. the [load program] dialog box is displayed. enter ?[installation directory]\tutorial\tutorial\debug\tutorial.abs? in the [file name] list box as shown in figure 3.6, then click the [open] button. figure 3.6 [load program] dialog box notes: 1. when installing the emulator, if no directory is specified and the hew is in use, the program is installed under ?\hew\hdi5\e10a?. when the hew is not in use, the program is installed under ?\root directory\e10a?. 2. the sni file is required so that the profiler function can be used. 3. the [verify] check box is disabled in this product. after the file has been loaded, the following dialog box displays information about the memory areas to which the program code has been transferred. figure 3.7 [hdi] dialog box ? click the [ok] button to continue.
rev. 2.0, 01/01, page 34 of 214 3.7.2 displaying the source program the hdi allows the user to debug a program at the source level. ? select [source...] from the [view] menu. the [open] dialog box is displayed. ? select the c source file that corresponds to the object file the user has loaded. figure 3.8 [open] dialog box ? select [tutorial.c] and click the [open] button. the [source] window is displayed.
rev. 2.0, 01/01, page 35 of 214 figure 3.9 [source] window (displaying the source program) ? if necessary, select the [font] option from the [customise] submenu on the [setup] menu to select a font and size that are legible. initially the [source] window shows the start of the main program, but the user can use the scroll bar to scroll through the program and look at the other statements.
rev. 2.0, 01/01, page 36 of 214 3.8 setting a software breakpoint a breakpoint is a simple debugging function. the [source] window provides a very simple way of setting a software breakpoint at any point in a program. for example, to set a breakpoint at the sort function call: ? select by double-clicking the [bp] column on the line containing the sort function call. figure 3.10 [source] window (setting a software breakpoint) the symbol ? will appear on the line containing the sort function, and the word ? break will appear when the [bp] column is extended. this shows that a software breakpoint has been set. note: the software breakpoint cannot be set in the rom area.
rev. 2.0, 01/01, page 37 of 214 3.9 setting registers set values of the program counter and the stack pointer before executing the program. ? select [registers] from the [view] menu. the [registers] window is displayed. figure 3.11 [registers] window
rev. 2.0, 01/01, page 38 of 214 ? to change the value of the program counter (pc), double-click the value area in the [registers] window with the mouse. the following dialog box is then displayed, and the value can be changed. set the program counter to h?0c00006c in this tutorial program, and click the [ok] button. ? move the mouse pointer on the value to be changed in the [pc] value area and enter the new value by the keyboard. figure 3.12 [register] dialog box (pc) ? change the value of the stack pointer (sp) in the same way. set h?0c000c00 for the value of the stack pointer in this tutorial program.
rev. 2.0, 01/01, page 39 of 214 3.10 executing the program execute the program as described in the following: ? to execute the program, select [go] from the [run] menu, or click the [go] button on the toolbar. figure 3.13 [go] button the program will be executed up to the breakpoint that has been inserted, and a statement will be highlighted in the [source] window to show the position that the program has halted, with the message [break=breakpoint] in the status bar. figure 3.14 [source] window (break status)
rev. 2.0, 01/01, page 40 of 214 the user can see the cause of the break that occurred last time in the [system status] window. ? select [status] from the [view] menu. after the [system status] window is displayed, open the [platform] page, and check the status of cause of last break. figure 3.15 [system status] window note: the items that can be displayed in this window differ according to the product. for the items that can be displayed, refer to the online help.
rev. 2.0, 01/01, page 41 of 214 3.11 reviewing breakpoints the user can see all the breakpoints set in the program in the [breakpoints] window. ? select [breakpoints] from the [view] menu. figure 3.16 [breakpoints] window the pop-up menu, opened by clicking the [breakpoints] window with the right mouse button, also allows the user to set or change breakpoints, define new breakpoints, and delete, enable, or disable breakpoints.
rev. 2.0, 01/01, page 42 of 214 3.12 viewing memory when the label name is specified, the user can view the memory contents that the label has been registered in the [memory] window. for example, to view the memory contents corresponding to the _main in word size: ? select [memory ?] from the [view] menu, enter _main in the [address] edit box, and set word in the [format] combo box. figure 3.17 [open memory window] dialog box ? click the [ok] button. the [memory] window showing the specified area of memory is displayed. figure 3.18 [memory] window
rev. 2.0, 01/01, page 43 of 214 3.13 watching variables as the user steps through a program, it is possible to watch that the values of variables used in the user program are changed. for example, set a watch on the long-type array a declared at the beginning of the program, by using the following procedure: ? click the left of displayed array a in the [source] window to position the cursor. ? click the [source] window with the right mouse button and select [instant watch...] from a pop-up menu. the following dialog box will be displayed. figure 3.19 [instant watch] dialog box
rev. 2.0, 01/01, page 44 of 214 ? click [add watch] button to add a variable to the [watch] window. figure 3.20 [watch] window (displaying the array) the user can also add a variable to the [watch] window by specifying its name. ? click the [watch] window with the right mouse button and select [add watch?] from the pop-up menu. the following dialog box will be displayed. figure 3.21 [add watch] dialog box ? input variable max and click the [ok] button.
rev. 2.0, 01/01, page 45 of 214 the [watch] window will now also show the int-type variable max . figure 3.22 [watch] window (displaying the variable) the user can double-click the + symbol to the left of any variable in the [watch] window to watch the all elements in array a . figure 3.23 [watch] window (displaying array elements)
rev. 2.0, 01/01, page 46 of 214 3.14 stepping through a program the hdi provides a range of step menu commands that allow efficient program debugging. table 3.2 step option menu command description step in executes each statement, including statements within functions. step over executes a function call in a single step. step out steps out of a function, and stops at the statement following the statement in the program that called the function. step? steps the specified times repeatedly at a specified rate. 3.14.1 executing [step in] command the [step in] steps into the called function and stops at the first statement of the called function. ? to step through the sort function, select [step in] from the [run] menu, or click the [step in] button in the toolbar. figure 3.24 [step in] button
rev. 2.0, 01/01, page 47 of 214 figure 3.25 [source] window (step in) ? the highlighted line moves to the first statement of the sort function in the [source] window.
rev. 2.0, 01/01, page 48 of 214 3.14.2 executing [step out] command the [step out] steps out of the called function and stops at the next statement of the calling statement in the main function. ? to step out of the sort function, select [step out] from the [run] menu, or click the [step out] button in the toolbar. note: it takes time to execute this function. figure 3.26 [step out] button figure 3.27 [hdi] window (step out) ? the data of variable a displayed in the [watch] window is sorted in ascending order.
rev. 2.0, 01/01, page 49 of 214 ? to execute two steps, use [step in] twice. figure 3.28 [hdi] window (step in ? ? ? ?> > > > ? the value of max displayed in the [watch] window is changed to the maximum data value.
rev. 2.0, 01/01, page 50 of 214 3.14.3 executing [step over] command the [step over] executes a function call as a single step and stops at the next statement of the main program. ? using [step over], execute two steps to reach the change function statement. figure 3.29 [source] window (before step over execution) ? to step through all statements in the change function at a single step, select [step over] from the [run] menu, or click the [step over] button in the toolbar. figure 3.30 [step over] button
rev. 2.0, 01/01, page 51 of 214 figure 3.31 [hdi] window (step over)
rev. 2.0, 01/01, page 52 of 214 3.15 forced breaking of program executions the hdi can force a break in the execution of a program. ? to execute the remaining sections of the main function, select [go] from the [run] menu or the [go] button on the toolbar. figure 3.32 [go] button ? the program goes into an endless loop. to force a break in execution, select [halt] from the [run] menu or the [stop] button on the toolbar. figure 3.33 [stop] button ? the highlighted line of the [program] window moves to the while statement, and the value of max displayed in the [watch] window is updated to the most recent value.
rev. 2.0, 01/01, page 53 of 214 3.16 displaying local variables the user can display local variables in a function using the [locals] window. for example, we will examine the local variables in the main function, which declares five local variables: a , j , i , min , and max . ? select [locals] from the [view] menu. the [locals] window is displayed. initially, the [locals] window is empty because local variables have not yet been declared. the [locals] window will now show the local variables and their values. figure 3.34 [locals] window ? double-click the + symbol in front of array a in the [locals] window to display the elements of array a . ? refer to the elements of array a before and after the execution of the sort function, and confirm that random data is sorted in descending order.
rev. 2.0, 01/01, page 54 of 214 3.17 break function the emulator has software and hardware break functions. with the hdi, a software breakpoint can be set using the [breakpoints] window, and a hardware break condition can be set using the [break condition] dialog box. an overview and setting of the break function are described below. 3.17.1 software break function the emulator can set up to 255 software breakpoints. other methods for setting a software breakpoint than in section 3.8 are described below. ? select [breakpoints] from the [view] menu. the [breakpoints] window is displayed. ? click the [breakpoints] window with the right mouse button and select [delete all] from the pop-up menu to cancel all the breakpoints that have been set. figure 3.35 [breakpoints] window (before software breakpoint setting)
rev. 2.0, 01/01, page 55 of 214 ? click the [breakpoints] window with the right mouse button and select [add] from the pop-up menu. the [break] dialog box is displayed. the [point] page is displayed as a default. figure 3.36 [point] page ([break] dialog box)
rev. 2.0, 01/01, page 56 of 214 ? click the [add...] button to display the [breakpoint] dialog box. ? enter h'0c0000c2 to the [value] edit box. figure 3.37 [break point] dialog box ? click the [ok] button.
rev. 2.0, 01/01, page 57 of 214 the [break] dialog box is displayed. the address set in the value field of [breakpoint] and the memory space are displayed. figure 3.38 [point] page ([break] dialog box) (after software breakpoint setting) ? click the [close] button (or [ok] button in some emulator products).
rev. 2.0, 01/01, page 58 of 214 the software breakpoint that has been set is displayed in the [breakpoints] window. figure 3.39 [breakpoints] window (software breakpoint setting) to stop the tutorial program at the breakpoint, the following procedure must be executed: ? close the [breakpoints] window. ? set the program counter and stack pointer values (pc = h?0c00006c and r15 = h?0c000c00) that have been set in section 3.9, setting registers, in the [registers] window. click the [go] button. the program runs, and stops at the set breakpoint. figure 3.40 [source] window at execution stop (software break)
rev. 2.0, 01/01, page 59 of 214 the [system status] window displays the following contents. figure 3.41 displayed contents of the [system status] window (software break) note: the items that can be displayed in this window differ according to the product. for the items that can be displayed, refer to the online help.
rev. 2.0, 01/01, page 60 of 214 3.18 hardware break function a method is given below in which the address bus condition and the read cycles for the bus status condition are set under break condition 1 as hardware break conditions. ? select [breakpoint window] from the [view] menu. the [breakpoints] window is displayed. ? click the [breakpoints] window with the right mouse button and select [delete all] from the pop-up menu to cancel all breakpoints that have been set. ? click the [breakpoints] window with the right mouse button and select [add] from the pop-up menu. figure 3.42 [breakpoints] window (before hardware break condition setting)
rev. 2.0, 01/01, page 61 of 214 the [break] dialog box is displayed. to set hardware break conditions, select [condition] in the [break] dialog box to display the [condition] page. figure 3.43 [condition] page ([break] dialog box) up to three breakpoints can be set independently for the break condition hardware break condition. in this example, set the hardware break condition for break condition 1. note: the number of hardware break conditions differs according to the product. for the number that can be specified for each product, refer to the online help. ? highlight the first point in the [break condition] list box. ? click the [edit...] button. the [break condition 1] dialog box is displayed.
rev. 2.0, 01/01, page 62 of 214 ? clear the [don't care] check box in the [address] page. ? select the [address] radio button and enter h'0c0000b2 as the value in the [address] edit box. figure 3.44 [address] page ([break condition 1] dialog box) note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 63 of 214 ? select [bus state] to display the [bus state] page. ? select the [read] radio button in the [read/write] group box. figure 3.45 [bus state] page ([break condition 1] dialog box) note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 64 of 214 ? click the [ok] button. ? the [break] dialog box is displayed, and the first point display in the [break condition] list box changes from empty to enable . figure 3.46 [break] dialog box (after hardware break condition setting) note: the number of hardware break conditions differs according to the product. for the number that can be specified for each product, refer to the online help. ? click the [ok] button.
rev. 2.0, 01/01, page 65 of 214 the newly set hardware breakpoint is displayed in the [breakpoints] window. with this setting, break condition 1 is displayed in [type] in the [breakpoints] window. this completes the setting of the break condition 1 hardware break condition. when the program is executed, a break will occur when address h'0c0000b2 is accessed in a read cycle. figure 3.47 [breakpoints] window ([break condition 1] setting) ? close the [breakpoints] window. ? set the program counter and stack pointer values (pc = h?0c00006c and r15 = h?0c000c00) that have been set in section 3.9, setting registers, in the [registers] window. click the [go] button.
rev. 2.0, 01/01, page 66 of 214 the program runs then stops at the condition specified under break condition 1. figure 3.48 [source] window at execution stop (break condition 1)
rev. 2.0, 01/01, page 67 of 214 the [system status] window displays the following contents. figure 3.49 displayed contents of the [system status] window (break condition 1) note: the items that can be displayed in this window differ according to the product. for the items that can be displayed, refer to the online help.
rev. 2.0, 01/01, page 68 of 214 3.18.1 setting the sequential break condition the emulator has sequential break functions. when the hardware break conditions listed in table 3.3 are satisfied, program execution is halted. this mode is called sequential break. table 3.3 sequential break conditions break condition description sequential break condition 2-1 program is halted when break condition 2 and break condition 1 are satisfied in that order. sequential break condition 2-1 is described below as an example. before executing the program, change setting in the [configuration] dialog box. otherwise, the sequential break does not function. ? select [configure platform...] from the [setup] menu. the [configuration] dialog box is displayed. ? select sequential break condition 2-1 from the [emulation mode] combo box.
rev. 2.0, 01/01, page 69 of 214 figure 3.50 [configuration] dialog box (sequential break setting) note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help. click the [ok] button and close the [configuration] dialog box.
rev. 2.0, 01/01, page 70 of 214 set hardware break conditions as follows: break condition 1: when address h'0c0000c6 is accessed in a read cycle, a break condition is satisfied. break condition 2: when address h'0c0000b2 is accessed in a read cycle, a break condition is satisfied. follow the setting method described in the previous section. ? when break condition 1,2 setting has been completed, the state of the [breakpoints] window is as follows. figure 3.51 [breakpoints] window (after sequential break condition setting) ? close the [breakpoints] window. ? set the program counter and stack pointer values (pc = h?0c00006c and r15 = h?0c000c00) that have been set in section 3.9, setting registers, in the [registers] window. click the [go] button.
rev. 2.0, 01/01, page 71 of 214 the program runs then stops at the condition specified under break condition 1. figure 3.52 [source] window at execution stop (sequential break)
rev. 2.0, 01/01, page 72 of 214 the [system status] window displays the following contents. figure 3.53 displayed contents of the [system status] window (sequential break) note: the items that can be displayed in this window differ according to the product. for the items that can be displayed, refer to the online help.
rev. 2.0, 01/01, page 73 of 214 3.19 trace functions the e10a emulator has two branch-instruction trace functions. (1) internal trace function the branch source and branch destination addresses, mnemonics, operands, and source lines are displayed. since this function uses the trace buffer built into the mcu, a realtime trace can be acquired. notes: 1. the number of branch instructions that can be acquired by a trace differs according to the product. for the number that can be specified for each product, refer to the online help. 2. the internal trace function is not supported for all products. for the specifications of each product, refer to the section related to the trace functions in section 6, shxxxx e10a emulator specifications, or to the online help. 3. the internal trace function is not extended for all products. for the specifications of each product, refer to the section related to the trace functions in section 6, shxxxx e10a emulator specifications, or to the online help. (2) aud trace function this is the large-capacity trace function that is enabled when the aud pin is connected to the emulator. this function displays the branch source and branch destination addresses, mnemonics, operands, and source lines. when the branch source and branch destination instructions are one branch, the number of branch instructions acquired by a trace is a maximum of 4,096 in the pcmcia-type emulator and a maximum of 16,384 in the pci-type emulator. table 3.4 shows the aud trace function. notes: 1. the aud trace function is not supported for all products. for the specifications of each product, refer to the section related to the trace functions in section 6, shxxxx e10a emulator specifications, or to the online help. 2. the aud trace function is not extended for all products. for the specifications of each product or the number of acquired branches, refer to the section related to the trace functions in section 6, shxxxx e10a emulator specifications, or to the online help.
rev. 2.0, 01/01, page 74 of 214 table 3.4 aud trace functions type mode description realtime trace when the next branch occurs while the trace information is being output, the output is stopped and the next trace information is output. the user program can be executed in realtime, but some trace information will not be output. acquisition mode when branches continuously occur non realtime trace when the next branch occurs while the trace information is being output, the cpu stops operations until the information is output. the user program is not executed in realtime. trace continue this function always overwrites the oldest trace information to acquire the latest trace information. acquisition mode when the trace buffer of the emulator becomes full trace stop the trace information is not acquired. the user program is continuously executed.
rev. 2.0, 01/01, page 75 of 214 3.19.1 internal trace function the branch source and branch destination information for the latest several branch instructions are displayed. the following is a procedure to set the internal trace function (this function is not needed to be set in the emulator that does not support the aud trace function): 1. select [trace] from the [view] menu. 2. click the [trace] window with the right mouse button and select [acquisition] from the pop- up menu to display the [trace acquisition] window. 3. select the [internal trace] radio button in the [trace type] group box. figure 3.54 [trace mode] window note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 76 of 214 run the program as shown in the example of section 3.17.1, software break function. the trace results are displayed in the [trace] window after the program execution is completed. figure 3.55 [trace] window ? if necessary, adjust the column width by dragging the header bar immediately below the title bar. note: the number of branch instructions that can be acquired by a trace differs according to the product. for the number that can be specified for each product, refer to the online help.
rev. 2.0, 01/01, page 77 of 214 3.19.2 aud trace function this function is operational when the aud pin of the mcu is connected to the emulator. the following is the procedure for setting the aud trace function (this function does not need to be set in an emulator that does not support the internal trace function): 1. select [trace] from the [view] menu. 2. click the [trace] window with the right mouse button and select [acquisition] from the pop- up menu to display the [trace acquisition] window. 3. select the [aud trace] radio button in the [trace type] group box. figure 3.56 [trace mode] window note: for a description of each option, refer to table 3.4. note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help. the trace results are displayed in the [trace] window after the program execution is completed. the display specifications in the [trace] window are the same as the internal trace function.
rev. 2.0, 01/01, page 78 of 214 the following is an example of the display in the sh7751 e10a emulator. figure 3.57 [trace] window in the sh7751 e10a emulator
rev. 2.0, 01/01, page 79 of 214 3.19.3 vp_map translation the mcu, which has an mmu, translates internal addresses (virtual addresses) to actual memory addresses (physical addresses). address translation is performed according to the address translation table (translation look-aside buffer: tlb) in the mcu. the mmu operates during command input wait state as well as during user program execution. when a command for memory access is executed while the mmu address translation function is enabled, the address translated by the mmu is accessed. if the specified address is not within the tlb, a tlb miss occurs, and the tlb must be updated by the user program. the emulator has address translation functions according to the vp_map tables. the vp_map tables are the address translation tables for the emulator created with the vpmap_set command. the following shows an example of how to use the vp_map tables. example: 1. create vp_map tables for translating virtual addresses h'10000 to h'10fff to physical addresses h'4000000 to h'4000fff and virtual addresses h'11000 to h'11fff to physical addresses h'0 to h'fff. > vs 10000 10fff 4000000 (ret) > vs 11000 11fff 0 (ret) > vd (ret) 00010000 00010fff 04000000 00011000 00011fff 00000000 disable 2. then, enable the vp_map tables. (when the tables are disabled, addresses are not translated.) > ve ;enable (ret) > vd (ret) 00010000 00010fff 04000000 00011000 00011fff 00000000 enable here, virtual addresses correspond to physical addresses as shown in figure 3.58.
rev. 2.0, 01/01, page 80 of 214 virtual address physical address h'10000 h'10fff h'11000 h'11fff h'12000 h'12fff h'12000 h'12fff h'4000000 h'4000fff h'0 h'fff figure 3.58 address translation according to vp_map tables how to translate addresses depends on the settings of the radio buttons of the memory area group in the [configuration] dialog box. the following shows how to translate addresses in each setting state. ? when the normal radio button is selected: the vp_map table has a priority over the tlb. when the vp_map table is enabled and the specified address is within the vp_map table settings, the emulator translates the address according to the vp_map table. if the specified address is outside the vp_map table settings even when the vp_map table is enabled, or when the vp_map table is disabled, the emulator translates the address according to the mmu state. ? when the virtual radio button is selected: the address is translated according to the tlb. if the specified address is outside the tlb table settings, a tlb error will occur. ? when the physical radio button is selected: the address is not translated.
rev. 2.0, 01/01, page 81 of 214 table 3.5 address translation tables vp_map mmu radio button* enabled/ disabled within/ outside the range enabled/ disabled within/outside the tlb range table used for translation within the range translated according to the vp_map table enabled outside the range translated according to the vp_map table within the range disabled within/outside the range translated according to the vp_map table within the range translated according to the tlb table enabled outside the range tlb error enabled outside the range disabled within/outside the range not translated within the range translated according to the tlb table enabled outside the range tlb error normal disabled within/ outside the range disabled within/outside the range not translated within the range translated according to the tlb table enabled outside the range tlb error within the range translated according to the tlb table virtual enabled/ disabled within/ outside the range disabled outside the range tlb error physical enabled/ disabled within/ outside the range enabled/ disabled within/outside the range not translated note: specified by the [memory area] group box in the [configuration] dialog box.
rev. 2.0, 01/01, page 82 of 214 3.20 stack trace function the emulator uses the stack?s information to display the name of the calling function for a function at which the program counter is currently pointing. notes: 1. this function can be used only when the load module that has the dwarf2-type debugging information is loaded. 2. for details on the stack trace function, refer to the online help. ? double-click the [bp] column in the sort function and set a software breakpoint. figure 3.59 [source] window (software breakpoint setting) ? set the same program counter and stack pointer values (pc = h?0c00006c and r15 = h?0c000c00) as were set in section 3.9, setting registers (again, use the [registers] window). click the [go] button. ? after the break in execution, select [stack trace] from the [view] menu to open the [stack trace] window.
rev. 2.0, 01/01, page 83 of 214 figure 3.60 [stack trace] window figure 3.60 shows that the position of the program counter is currently at the selected line of the sort() function, and that the sort() function is called from the main() function. notes: 1. if the function is not deeply nested (lower than 10), the main() function will be displayed multiple times. 2. for details on this function, refer to the online help. the online help is opened when the [f1] key is pressed in the [stack trace] window.
rev. 2.0, 01/01, page 84 of 214 3.21 profiling function the profile function can measure performance for each function. notes: 1. realtime operation is not possible while this function is in operation, since internal breaks are generated during program execution. measuring the profile itself affects the measurements. for details, refer to section 6, shxxxx emulator specifications. 2. when this function is to be used, click the [load stack information file (sni file)] check box in the [load program] dialog box to load the stack information file. 3. performance profile measurement is not supported for all products. on those products for which it is supported, its characteristics differ according to the product. for specifications for each product, refer to the section related to the trace functions in section 6, shxxxx e10a emulator specifications, or to the online help file. 4. for details, refer to section 13 in the hitachi debugging interface user?s manual. ? select [profile-list] from the [view] menu to open the [profile-list] window. a different set of data to be measured can be set for each function. figure 3.61 [profile-list] window
rev. 2.0, 01/01, page 85 of 214 ? the profile function is now enabled. place the mouse cursor on an entry in the [profile-list] window, click the right-hand mouse button, then select [enable profiler] from the pop-up menu. figure 3.62 selection of [enable profiler]
rev. 2.0, 01/01, page 86 of 214 ? data to be measured for the selected function is now set. select [select data] from the pop-up menu by clicking with the right mouse button. the [select data] dialog box is displayed. figure 3.63 [select data] dialog box ? use the [select data] dialog box to select the data to be measured. [all operand access count] is selected for data1 as a first item to be measured. [elapsed-time cycle] is selected for data2 as a second item to be measured. ? after the data has been selected, press the [ok] button. ? double-click the [bp] column for the while statement of the main function to set a software breakpoint.
rev. 2.0, 01/01, page 87 of 214 figure 3.64 [source] window (software break setting) ? set the same program counter and stack pointer values (pc = h?0c00006c and r15 = h?0c000c00) as were set in section 3.9, setting registers (again, use the [registers] window). click the [go] button. ? after the break in execution, the results of the measurements are displayed in the [profile-list] window. figure 3.65 [profile-list] window
rev. 2.0, 01/01, page 88 of 214 ? figures 3.66 and 3.67 show the [profile-tree] and [profile-chart] windows, respectively. figure 3.66 [profile-tree] window figure 3.67 [profile-chart] window
rev. 2.0, 01/01, page 89 of 214 3.22 download function to the flash memory area the e10a emulator enables downloading to the flash memory area. this function requires a program for writing the flash memory (hereinafter referred to as a write module), a program for erasing the flash memory (hereinafter referred to as an erase module), and the ram area for downloading and executing these modules. note: the write/erase module must be prepared by users. ? interface with write/erase module and e10a emulator firmware the write/erase module is branched from the e10a emulator firmware. to branch from the e10a emulator firmware to the write/erase module or to return from the write/erase module to the e10a emulator firmware, the following conditions must be observed: ? describe all the write/erase modules with the assembly language. ? guarantee all the general/control register values before and after calling the write/erase module. ? return the write/erase module to the calling source after processing. the module interface must be as follows to pass correctly the information that is required for flash memory accessing. table 3.6 module interface module name argument return value write module r4(l): write address r7(l): verify option 0 = no verify, 1 = verify r5(l): access size 0x4220 = byte, 0x5720 = word, 0x4c20 = longword r6(l): write data r0(l): end code normal end = 0, abnormal end = other than 0, verify error = bt erase module r4(l): access size 0x4220 = byte, 0x5720 = word, 0x4c20 = longword none note: the (l) means the longword size. note: write module: the write data for the access size is set to the r6 register. when the access size is word or byte, 0 is set to the upper bit of the r6 register.
rev. 2.0, 01/01, page 90 of 214 ? flash memory download method it is required to perform necessary settings on the [loading flash memory] page in the [configuration] window for downloading to the flash memory. figure 3.68 [loading flash memory] page
rev. 2.0, 01/01, page 91 of 214 table 3.7 shows the options for the [loading flash memory] page. table 3.7 [loading flash memory] page options option description [loading flash memory] radio button sets enable for flash memory downloading. at enable, when [file load] is selected from the [file] menu for downloading, the write module is always called. enable: download to the flash memory disable: not download to the flash memory [erasing flash memory] radio button sets enable for erasing before the flash memory is written. at enable, the erase module is called before calling the write module. enable: erase the flash memory disable: not erase the flash memory [file name] edit box sets the write/erase module name. the file that has been set is loaded to the ram area before loading to the flash memory. a maximum of 128 characters can be input for the file name. [bus width of flash memory] list box sets the bus width of the flash memory. [flash memory erasing time] edit box* sets the timeout value at flash memory erasing. increase the value if erasing requires much time; the default time is three minutes. the radix for the input value is decimal. it becomes hexadecimal by adding h?. [entry point] group box sets the calling destination address of the write/erase module. [all erasing module address] edit box: inputs the calling destination address of the erase module. [writing module address] edit box: inputs the calling destination address of the write module. note: although the values that can be set are d'0 to d'65535, the timeout hours may be extended according to the set value. therefore, it is recommended to input the minimum value. the value to be input must only be positive integer. ? notes on using the flash memory download function the following are notes on downloading to the flash memory. ? when the flash memory download is enabled, downloading other than to the flash memory area is disabled. ? downloading is only enabled to the flash memory area. perform memory write or software break only to the ram area. ? when the flash memory erase is enabled, the [stop] button cannot stop erasing. ? the area for the write/erase module must be mmu-disabled space.
rev. 2.0, 01/01, page 92 of 214 ? examples of downloading to the flash memory the following shows examples of downloading to the flash memory manufactured by intel corporation (type number: g28f640j5-150) that has been mounted on hitachi's sh7751 cpu board (type number: hs7751stc01h). a sample is provided in the \fmtool folder in the installation destination folder. create the program for user specification according to this sample. the sh7751 e10a emulator must be used when the sh7751 cpu board is used. table 3.8 example of board specifications item contents sdram address h'0c000000 to h'0fffffff flash memory address h'01000000 to h'01ffffff bus width of flash memory 32 bits cpu internal frequency 167 mhz bus frequency 55.7 mhz cpu internal module frequency 27.83 mhz operating environments endian big endian flash memory (32 mbytes) a0-a22 shxxxx ce0 ce1,2 oe we d0-d7 d8-d15 d0-d7 d8-d15 d0-d7 d8-d15 d0-d7 d8-d15 fpga fia bus buffer fia bus buffer fd bus buffer a2-a24 cs0 cs2 rd we0 d0-d31 gnd 0-7 8-15 16-23 24-31 figure 3.69 flash memory wiring
rev. 2.0, 01/01, page 93 of 214 table 3.9 sample program specifications item contents ram area to be used h'0c001000 to h'0c0015bf write module start address h'0c001100 erase module start address h'0c001000 (i) since the sdram is used, the bus controller is set. (ii) options on the [loading flash memory] page in the [configuration] window are set as follows: figure 3.70 [loading flash memory] page
rev. 2.0, 01/01, page 94 of 214 notes: 1. when the data has already been written in the flash memory, be sure to select [enable] for [erasing flash memory]. if [disable] is selected, a verify error occurs. 2. when [erasing flash memory] is selected, it takes about one minute. (iii) [load program?] is selected from the [file] menu for downloading to the flash memory area.
rev. 2.0, 01/01, page 95 of 214 3.23 what next? this tutorial has described the major features of the emulator and the use of the hdi. sophisticated debugging can be carried out by using the emulation functions that the emulator offers. this provides for effective investigation of hardware and software problems by accurately isolating and identifying the conditions under which such problems arise. further details on the use of the hdi can be found in the separately issued hitachi debugging interface user's manual.
rev. 2.0, 01/01, page 96 of 214
rev. 2.0, 01/01, page 97 of 214 section 4 descriptions of windows 4.1 hdi windows hdi window menu bars and the corresponding pull-down menus are listed in table 4.1. where a description of a menu is included in the hitachi debugging interface user's manual or in this manual, a o mark or the relevant section number is shown. related commands in the e10a emulator user's manual are also shown. table 4.1 hdi window menus and related manual entries menu bar pull-down menu hitachi debugging interface user's manual this manual new session? o ? load session? o ? save session o 2.6 save session as? o ? load program? o 3.7.1 initialize o ? file menu exit o ? cut o ? copy o ? paste o ? find? o ? edit menu evaluate? o ?
rev. 2.0, 01/01, page 98 of 214 table 4.1 hdi window menus and related manual entries (cont) menu bar pull-down menu hitachi debugging interface user's manual this manual breakpoints o 3.11, 3.17.1, 4.2.4, 6.5.5 command line o ? disassembly... o ? i/o area o ? labels o ? locals o 3.16 memory... o 3.12 performance analysis o ? profile-list o 3.21 profile-tree o 3.21 registers o 3.9 source? o 3.7.2 stack trace x 3.20 status o 3.10, 3.17.1, 4.2.9 trace o 4.2.7, 6.5.3, 6.5.7 view menu watch o 3.13 reset cpu o ? go o 3.10 reset go o ? go to cursor o ? set pc to cursor o ? run? o ? step in o 3.14.1 step over o 3.14.3 step out o 3.14.2 step? o ? run menu halt o ?
rev. 2.0, 01/01, page 99 of 214 table 4.1 hdi window menus and related manual entries (cont) menu bar pull-down menu hitachi debugging interface user's manual this manual refresh o ? load o ? save o ? verify o ? test o ? fill o ? copy o ? memory menu compare o ? status bar o ? options o ? radix o ? customise o ? setup menu configure platform? o 3.5, 4.2 cascade o ? tile o ? arrange icons o ? window menu close all o ? index o ? using help o ? search for help on o ? help menu about hdi o ?
rev. 2.0, 01/01, page 100 of 214 4.2 descriptions of each window this section describes each window. figures in this section are used as examples. each e10a emulator type has explanatory notes. read section 6, shxxxx e10a emulator specifications. 4.2.1 [configuration] dialog box function: this dialog box sets the emulation conditions of the emulator. window: figure 4.1 [configuration] dialog box note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 101 of 214 description: the [configuration] dialog box consists of the [general] page listed in table 4.2. table 4.2 [configuration] dialog box page page name description [general] sets and displays the emulation mode conditions. [loading flash memory] sets the download function for the flash memory. clicking the [ok] button sets the emulation conditions. if the [cancel] button is clicked, this dialog box is closed without setting the emulation conditions.
rev. 2.0, 01/01, page 102 of 214 (1) [general] page ([configuration] dialog box) function: this page sets the emulator operation conditions, displays the device name, sets the emulation mode, ubc mode, and memory area (only for a product that supports a device with the mmu function), sets and displays the aud clock (audck) and jtag clock (tck), and selects the driver. window: figure 4.2 [general] page ([configuration] dialog box) note: the items and displayed contents that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 103 of 214 description: table 4.3 [general] page options option description [mode] combo box displays the device name. [emulation mode] combo box selects the execution mode. select normal to perform normal emulation. select no break to disable breakpoint settings. select sequential break condition 2-1, etc. to use the sequential break function* 1 . (for sequential break condition 2- 1, execution stops when conditions are satisfied in the order of break condition 2 and break condition 1.) [step option] combo box enables or disables interrupts during step execution. disables interrupts during single step execution: interrupts during step execution are masked. enables interrupts during single step execution: interrupts during step execution are released. [ubc mode] combo box eml: the ubc is used as a break condition by the emulator. user: the ubc is released for users. in this case, the [break condition] page becomes non-active. [memory area] group box sets the address setting mode to the memory area. the default is normal. when the vp_map is enabled and the address is within the table range, address translation is done according to the vp_map table. for other cases, address translation is done according to the mmu state. select physical when setting with a physical address. select virtual when address translation is done by the tlb table. [aud clock] combo box selects the aud clock* 2 . [jtag clock] combo box sets the jtag frequency* 3 . [driver] group box displays the driver currently selected. [change...] button displays the [e10a driver details] dialog box. use when a driver currently connected is changed. notes: 1. when using the sequential break function, set the corresponding hardware break conditions. 2. the range of frequencies that the aud operates under is different according to the devices used. for details, refer to section 6.5.4, notes on using the jtag clock (tck) and aud clock (audck). 3. the range of frequencies that the jtag operates at is different according to the devices used. for details, refer to section 6.5.4, notes on using the jtag clock (tck) and aud clock (audck).
rev. 2.0, 01/01, page 104 of 214 when a driver is to be changed with the [change..] button, the following message is displayed. figure 4.3 warning message box when the [yes] button is clicked, the [e10a driver details] dialog box is displayed. when the [no] button is clicked, the display returns to the [configuration] dialog box. related command: go_option command
rev. 2.0, 01/01, page 105 of 214 (2) [e10a driver details] dialog box function function: when the [change] button in the [driver] group box is clicked on the [general] page in the [configuration] dialog box, the [e10a driver details] dialog box is displayed. figure 4.4 [e10a driver details] dialog box description: table 4.4 options for the [e10a driver details] dialog box option description [driver] combo box selects the driver to connect the hdi with the emulator. selects [e10a pc card driver] to use the pcmcia card emulator. selects [e10a pci card driver] to use the pci card emulator. for details, refer to section 6.5.1, emulator driver selection. [interface] combo box displays the interface name of the card emulator to be connected. selects [pc card] to use the pcmcia card emulator. selects [pci] to use the pci card emulator. (if the driver is not installed, the [pc card] or [pci] is not displayed.) [channel] combo box displays the interface to which the board is connected.
rev. 2.0, 01/01, page 106 of 214 (3) [loading flash memory] page ([configuration] dialog box) function: downloading to the flash memory is set on the [loading flash memory] page. window: figure 4.5 [loading flash memory] page ([configuration] dialog box)
rev. 2.0, 01/01, page 107 of 214 description: table 4.5 [loading flash memory] page options option description [loading flash memory] radio button sets enable for flash memory downloading. at enable, when [file load] is selected from the [file] menu for downloading, the write module is always called. enable: download to the flash memory disable: not download to the flash memory [erasing flash memory] radio button sets enable for erasing before the flash memory is written. at enable, the erase module is called before calling the write module. enable: erase the flash memory disable: not erase the flash memory [file name] edit box sets the write/erase module name. the file that has been set is loaded to the ram area before loading to the flash memory. a maximum of 128 characters can be input for the file name. [bus width of flash memory] list box sets the bus width of the flash memory. [flash memory erasing time] edit box* sets the timeout value at flash memory erasing. increase the value if erasing requires much time; the default time is three minutes. the radix for the input value is decimal. it becomes hexadecimal by adding h?. [entry point] group box sets the calling destination address of the write/erase module. [all erasing module address] edit box: inputs the calling destination address of the erase module. [writing module address] edit box: inputs the calling destination address of the write module. note: although the values that can be set are d'0 to d'65535, the timeout hours may be extended according to the set value. therefore, it is recommended to input the minimum value. the value to be input must only be positive integer. notes on using the flash memory download function the following are notes on downloading to the flash memory. ? when the flash memory download is enabled, downloading other than to the flash memory area is disabled. ? downloading is only enabled to the flash memory area. perform memory write or software break only to the ram area. ? when the flash memory erase is enabled, the [stop] button cannot stop erasing. ? the entry area for the user module must be mmu-disabled space.
rev. 2.0, 01/01, page 108 of 214 4.2.2 [breakpoints] window function: this window lists all break conditions that have been set. window: figure 4.6 [breakpoints] window
rev. 2.0, 01/01, page 109 of 214 description: the [breakpoints] window displays breakpoint setting information. the items listed in the following tables are displayed. table 4.6 [breakpoints] window display items item description [enable] displays whether the break condition is enabled or disabled. breakpoint: ? break condition: o (if the address is the same as the one that has been set to the breakpoint, the mark is ? .) [file/line] displays the file name and line number where the breakpoint is set. [symbol] displays the symbol corresponding to the breakpoint address. if no symbol has been defined for the address, nothing is displayed. [address] displays the address where the breakpoint is set. [type] displays the break condition type as follows: break point: software breakpoint (virtual or physical address is determined according to the mmu state at setting.) break point virtual space asid = d'xxx: software breakpoint (virtual address. asid value is displayed in decimal.) break point physical space: software breakpoint (physical address.) break condition 1 to break condition 3: hardware break condition note: only "break point" is displayed in the [type] item when the device does not support the mmu.
rev. 2.0, 01/01, page 110 of 214 the pop-up menu, which is opened by clicking the right mouse button, can be used to set, change, and clear breakpoints, and to enable or disable break conditions. the pop-up menu functions are described in the following table. table 4.7 [breakpoints] window pop-up menu operation menu name description [add] sets break conditions. clicking this button will display the [break] dialog box, enabling break conditions to be set. [edit] changes break conditions. select break conditions to be changed and click this button. the break condition setting dialog box will be displayed, enabling the break condition to be changed. [disable] ([enable]) enables or disables break conditions. select break conditions to be enabled or disabled and click this button. [delete] clears break conditions. select break conditions to be cleared and click this button. [del all] clears all break conditions. [go to source] jumps to the address which sets the break in the [source] window.
rev. 2.0, 01/01, page 111 of 214 4.2.3 [break] dialog box function: this dialog box displays the break condition settings. window: figure 4.7 [break] dialog box
rev. 2.0, 01/01, page 112 of 214 description: the [break] dialog box consists of the pages listed in table 4.8. table 4.8 [break] dialog box pages page name description [point] displays software breakpoint settings. [condition] displays break condition settings. the dialog boxes which set or modify break conditions can be displayed from the pages above. clicking the [ok] button (or [close] button in some emulator products) will close this dialog box.
rev. 2.0, 01/01, page 113 of 214 (1) [point] page ([break] dialog box) function: this page displays software breakpoint settings. in this page, software breakpoints can be set, changed, and cleared. window: figure 4.8 [point] page ([break] dialog box)
rev. 2.0, 01/01, page 114 of 214 description: table 4.9 [point] page options option description [break point] list box lists the software breakpoints currently being set. the display contents are and

is displayed as follows: ? physical space ? virtual space asid = d?xxx (xxx is the asid value displayed in decimal form.) [add...] button sets software breakpoints. clicking this button displays the [break point] dialog box. [edit...] button changes the software breakpoint selected in the [break point] list box. clicking this button displays the [break point] dialog box. [reset] button clears the software breakpoint selected in the [break point] list box. [reset all] button clears all software breakpoints displayed in the [break point] list box. related commands: breakpoint command breakpoint_clear command breakpoint_enable command breakpoint_display command
rev. 2.0, 01/01, page 115 of 214 (2) [condition] page ([break] dialog box) function: this page displays the break condition settings. these conditions can also be set or cleared in this page. window: figure 4.9 [condition] page ([break] dialog box) note: the number of hardware break conditions differs according to the product. for the number that can be specified for each product, refer to the online help.
rev. 2.0, 01/01, page 116 of 214 description: table 4.10 [condition] page options option description [break condition] list box displays the break condition settings. the display at system initiation is as follows: when conditions are set, enable is displayed. when no conditions are set, empty is displayed. 1 empty (setting of break condition 1) 2 empty (setting of break condition 2) : [edit...] button changes the break condition settings selected in the [break condition] list box. clicking this button displays the [break condition] dialog boxes. [reset] button clears the break condition settings selected in the [break condition] list box. [reset all] button clears all break condition settings in the [break condition] list box. related commands: breakcondition_clear command breakcondition_display command breakcondition_enable command breakcondition_set command
rev. 2.0, 01/01, page 117 of 214 4.2.4 [break point] dialog box function: this dialog box sets software breakpoints. window: figure 4.10 [break point] dialog box note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 118 of 214 description: the [break point] dialog box consists only of the [address] page. this dialog box sets address conditions and address areas. the [address] page options are as follows: table 4.11 [address] page options option description [value] edit box sets a breakpoint address with a number or a symbol. [normal] radio button does not set an address area.* [physical space] radio button shows that the break condition is the physical area.* [virtual space] radio button shows that the break condition is the virtual area.* [asid] edit box sets an asid value (0 to 255) when the breakpoint address is in the virtual area. nothing is set as default.* note: these options are not supported in a device in which the mmu is not built-in. clicking the [ok] button enables breakpoints to be set. if the [cancel] button is clicked, this dialog box is closed without setting breakpoints. related commands: breakpoint command breakpoint_clear command breakpoint_display command breakpoint_set command
rev. 2.0, 01/01, page 119 of 214 4.2.5 [break condition] dialog box function: this dialog box sets hardware break conditions. window: figure 4.11 [break condition] dialog box note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 120 of 214 description: the [break condition] dialog box consists of multiple pages. a condition to halt the program can be set in each page. contents to be set by each page are described in section 4.2.6, [break condition] dialog box pages. clicking the [ok] button sets the hardware break conditions. if the [cancel] button is clicked, the dialog box is closed without setting the hardware break conditions. related commands: breakcondition_clear command breakcondition_display command breakcondition_enable command breakcondition_set command
rev. 2.0, 01/01, page 121 of 214 4.2.6 [break condition] dialog box pages function: the [break condition] dialog box pages allow a number of hardware break conditions to be set. some functions may not be supported by some types of emulators. the setting conditions may differ from the dialog box name in table 4.12. for details, refer to section 6.5.2, break condition functions. table 4.12 setting conditions in [break condition] dialog boxes type dialog box address bus condition data bus condition bus state and read/write conditions count condition ldtlb instruction break and internal i/o access break conditions [break condition 1] dialog box oo o o x [break condition 2] dialog box ox o x x [break condition 3] dialog box xx x x o note: o: can be set by checking the radio button in the dialog box. x: cannot be set in the dialog box.
rev. 2.0, 01/01, page 122 of 214 table 4.13 shows all the [break condition] dialog box pages. table 4.13 [break condition] dialog box pages page name function [address] sets the address conditions of break condition 1 and break condition 2. (address condition is not displayed in the [break condition 3] dialog box page.) [data] sets the data conditions of break condition 1. (data condition is not displayed in the [break condition 2] and [break condition 3] dialog box pages.) [asid] sets the asid conditions of break condition 1 and break condition 2. (asid condition is not displayed in the [break condition 3] dialog box page.) [bus state] sets the bus state conditions and read/write cycle conditions of break condition 1 and break condition 2. (bus state condition is not displayed in the [break condition 3] dialog box page.) [count] sets the satisfaction count conditions of break condition 1. (count condition is not displayed in the [break condition 2] and [break condition 3] dialog box pages.) [general] sets the conditions of break condition 3. (data condition is not displayed in the [break condition 1] and [break condition 2] dialog box pages.) note: this function differs according to the product. for the specifications of each product, refer to section 6.5.2, break condition functions, or to the online help.
rev. 2.0, 01/01, page 123 of 214 (1) [address] page ([break condition] dialog box) function: this page sets the address bus conditions. window: figure 4.12 [address] page ([break condition 1] dialog box) note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 124 of 214 description: table 4.14 [address] page options option description [don?t care] check box does not set address conditions. [address] radio button sets use of the normal address bus as break conditions. [only program fetched address] radio button sets a break before prefetched address execution as break conditions. [only program fetched address after] radio button sets a break after prefetched address execution as break conditions. [x-bus address] radio button sets the x-bus address as a break condition. can be set only with break condition 1. [y-bus address] radio button sets the y-bus address as a break condition. can be set only with break condition 1. [address] edit box sets the address bus value with a number or a symbol. [non user mask] radio button sets no mask conditions. [user mask] radio button sets mask conditions. [mask] edit box sets the mask bits if [user mask] is selected. for masked bits, the break condition is satisfied regardless of the address values. note: this page is displayed when the conditions of break condition 1 and break condition 2 are set. a page name to be displayed and the contents of an option that can be set will change depending on the radio button selected. table 4.15 address options option description [address] radio button, [x-bus address] radio button, and [y-bus address] radio button all pages can be selected and masks can be set. [only program fetched address] radio button the [address] and [asid] pages can be set; however, no mask can be set. [only program fetched address after] radio button the [address] and [asid] pages can be set. note: this function differs according to the product. for the specifications of each product, refer to section 6.5.2, break condition functions, or to the online help.
rev. 2.0, 01/01, page 125 of 214 (2) [data] page ([break condition] dialog box) function: this page sets the data bus conditions. window: figure 4.13 [data] page ([break condition 1] dialog box) note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 126 of 214 description: table 4.16 [data] page options option description [don?t care] check box does not set data conditions. [value] edit box sets the data bus value with a number. [byte] radio button sets byte data access cycles. [word] radio button sets word data access cycles. [long] radio button sets longword data access cycles. [x-bus data] radio button sets x-bus data access cycles. [y-bus data] radio button sets y-bus data access cycles. [non user mask] radio button does not set mask conditions. [user mask] radio button sets mask conditions. [mask] edit box sets the mask bits when [user mask] is selected. mark a bit to be masked with *. for masked bits, the break conditions will be satisfied regardless of the data values. note: this page is displayed when the conditions of break condition 1 are set.
rev. 2.0, 01/01, page 127 of 214 (3) [asid] page ([break condition] dialog box) function: this page sets the asid conditions. window: figure 4.14 [asid] page ([break condition] dialog box) description: table 4.17 [asid] page options option description [don?t care] check box does not set asid conditions. [asid] edit box sets the asid condition value. the default is 0. note: this page is displayed when the conditions of break condition 1 and break condition 2 are set. note: these options are not supported in a device in which the mmu is not built-in.
rev. 2.0, 01/01, page 128 of 214 (4) [bus state] page ([break condition] dialog box) function: this page sets bus state conditions and read/write cycle conditions. window: figure 4.15 [bus state] page ([break condition] dialog box) note: the items that can be set in this window differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 129 of 214 description: table 4.18 [bus state] page options group box option description [all] radio button sets the bus state conditions as break conditions. [data] radio button sets the execution cycle as break conditions. [bus state] group box [dma] radio button sets dma cycles as a break condition. [read/write] radio button sets the read/write cycle conditions as break conditions. [read] radio button sets read cycles as break conditions. [read/write] group box [write] radio button sets write cycles as break conditions. note: this page is displayed when the conditions of break condition 1 and break condition 2 are set.
rev. 2.0, 01/01, page 130 of 214 (5) [count] page ([break condition] dialog box) function: this page sets the conditions for break condition 1. window: figure 4.16 [count] page ([break condition] dialog box) table 4.19 [count] page options option description [don?t care] check box sets no satisfaction count conditions. input area sets the satisfaction count as a break condition. the maximum count is 4,095. breaks when the conditions set by the [break condition] dialog box for the specified times are satisfied. the default is d?1. note: some products are not supported by this function. for the specifications of each product, refer to the online help.
rev. 2.0, 01/01, page 131 of 214 (6) [general] page ([break condition] dialog box) function: this page sets the conditions for break condition 3. window: figure 4.17 [general] page ([break condition] dialog box)
rev. 2.0, 01/01, page 132 of 214 description: table 4.20 [general] page options group box option description [don?t care] radio button does not set break conditions when the ldtlb instruction is executed. [stop after executing ldtlb instruction] radio button sets the ldtlb instruction execution as break conditions. [ldtlb] group box [dma] radio button sets the dma cycle as break conditions. [don?t care] radio button does not set break conditions when the internal i/o area is accessed. [stop on accessing internal i/o area] radio button sets the internal i/o area access as break conditions. [i/o] group box [write] radio button sets only write cycle as break conditions. note: some products are not supported by this function. for the specifications of each product, refer to the online help.
rev. 2.0, 01/01, page 133 of 214 4.2.7 [trace] window function: this window displays the trace buffer contents. window: figure 4.18 [trace] window note: the types of information and the number of branch instructions differ according to the product. for the settings for each product, refer to the online help.
rev. 2.0, 01/01, page 134 of 214 description: this window displays the trace buffer contents. the items listed in table 4.21 are displayed. table 4.21 [trace] window display items item description [no.] displays the number in ascending order as the trace stop point is 0 (signed decimal). [ip] displays the instruction pointer (signed decimal). [type] for the branch instruction trace, displays the information type, that is, branch source or branch destination. branch: branch source destination: branch destination [addr/data] for the branch instruction trace, displays the branch source or branch destination address. [mnemonic] displays the execution instruction mnemonic. [operand] displays the execution instruction operand. [source] displays the c-source line of the address that the trace has been acquired. the pop-up menu, opened by clicking the right mouse button, can be used to set, change, and clear trace conditions. for details, refer to the hitachi debugging interface user?s manual. notes: 1. in some cases, the emulator address may be acquired by trace. in such a case, the following message will be displayed. ignore this address because it is not a user program address. *** eml *** 2. the [halt] menu in the pop-up menu is active only when the [trace] window is open during user program execution. when the internal trace is used, realtime emulation cannot be performed by using the [halt] menu. related command: trace_display command
rev. 2.0, 01/01, page 135 of 214 4.2.8 [trace acquisition] dialog box function: this dialog box sets trace acquisition conditions. when the [acquisition] menu is selected from the pop-up menu, which is displayed by clicking the right mouse button in the [trace] window, the [trace acquisition] dialog box is displayed. table 4.22 [trace acquisition] dialog box page options page name description [trace mode] sets the conditions of trace mode.
rev. 2.0, 01/01, page 136 of 214 (1) [trace mode] page ([trace acquisition] dialog box) function: this page sets the conditions for trace mode. window: figure 4.19 [trace mode] page ([trace acquisition] dialog box) note: this function differs according to the product. for the specifications of each product, refer to the section related to the trace functions in section 6, shxxxx e10a emulator specifications, or to the online help.
rev. 2.0, 01/01, page 137 of 214 description: table 4.23 [trace mode] page options option description [aud trace] radio button uses aud trace functions. by default, this box is not checked. [internal trace] radio button uses the internal trace functions. by default, this box is checked. [realtime trace] radio button when the next branch occurs while the trace information is being output, the information is stopped and the next trace information is output. the user program can be executed in realtime, but some trace information will not be output. by default, this box is checked. [non realtime trace] radio button when the next branch occurs while the trace information is being output, the cpu stops operations until the information is output. the user program is not executed in realtime. by default, this box is not checked. [trace continue] radio button when the trace buffer becomes full, this function always overwrites the oldest trace information to acquire the latest trace information. [trace stop] radio button when the trace buffer becomes full, the trace information is not acquired. [aud trace display range] group box inputs the start or end pointer value in the trace display range as numerical values. by default, the start pointer is ?d?8191 and the end pointer is ?d?0000. in the pcmcia card emulator, ?d?8191 to d?0 can be set to the trace pointer. in the pci card emulator, ?d?32767 to d?0 can be set. related command: aud_mode command
rev. 2.0, 01/01, page 138 of 214 4.2.9 [system status] window function: this window lists information, such as conditions that have been set to the emulator and execution results. window: figure 4.20 [system status] window note: the items that can be displayed in this window differ according to the product. for the items that can be displayed, refer to the online help.
rev. 2.0, 01/01, page 139 of 214 the items listed in the following table are displayed in the [system status] window. table 4.24 [system status] window display items page item description target system always displays connected. session name displays the session file name. [session] program name displays the load module file name. connected to displays the name of the connected emulator and the selected driver name. cpu displays the target device name. run status displays the execution status: running: being executed break: stopped cause of last break displays the cause of the emulator stopping at break. in this example, the cause of the stop is break point. run time count displays the program execution time. the display format is h: hours, min: minutes, s: seconds, and ms: milliseconds. in this example, 0h:0min:0s:16ms is displayed. emulator mode displays the emulator operating mode (setting information for [emulation mode] of the [configuration] dialog box). big endian/little endian displays the endian state (big endian or little endian). in this example, big endian is displayed. [platform] aud displays whether the aud function can be used. this item is displayed by the emulator with the aud function. [memory] loaded memory areas displays the loaded area of the load module. [events] resources displays the usage states of breakpoint and break condition.
rev. 2.0, 01/01, page 140 of 214
rev. 2.0, 01/01, page 141 of 214 section 5 command-line functions 5.1 table and symbol description this section describes the format used in section 5.2, command descriptions. the descriptions of some commands are given over two or more pages. 5.1.1 format the input format for each command is as follows. characters shown in bold-italics are to be input. [ ] : parameters enclosed by [ ] can be omitted. < > : contents shown in < > are set. < >=: the parameter to the left of the "=" sign is input in the format shown to the right. | : this represents a non-exclusive selection. | | : this represents an exclusive selection. the command parameter details are described in the parameter table. 5.1.2 parameter input numerical parameters: a binary, octal, decimal, or hexadecimal value, a symbol, or a formula can be input. a symbol can contain up to 32 characters. terms in a formula are separated with operators (such as + or ?). keyword parameters: one of the bold characters given in the description column of the table can be input. if a character string not shown in the description is input, an error will occur. character-string parameters: character-string parameters are used to input mask data or a file name. in the mask data, set a radix (h?: hexadecimal or b?: binary) at the top of a character string and set * at the digit to be masked.
rev. 2.0, 01/01, page 142 of 214 5.1.3 examples these are actual input examples. for commands whose execution results in a specific display output, an example of the display is given. 5.1.4 related items related e10a hdi commands (abbreviations) and dialog boxes are shown. (refer to section 4, descriptions of windows.)
rev. 2.0, 01/01, page 143 of 214 5.2 command descriptions the command list of the e10a emulator is shown below. table 5.1 e10a hdi commands no. command abb. function 1 aud_clock aucl sets the aud clock (audck). 2 aud_mode aum sets aud trace conditions. 3 aud_trace aut displays trace information. 4 breakcondition_ clear bcc clears hardware breakpoints that have been set. 5 breakcondition_ display bcd displays hardware breakpoints that have been set. 6 breakcondition_ enable bce enables or disables hardware breakpoints that have been set. 7 breakcondition_ set bcs sets hardware breakpoints. 8 breakpoint bp sets software breakpoints. 9 breakpoint_clear bc clears software breakpoints that have been set. 10 breakpoint_display bd displays software breakpoints that have been set. 11 breakpoint_enable be enables or disables software breakpoints that have been set. 12 device_type de displays device type currently selected. 13 go_option gp displays or sets the emulation mode during user program execution. 14 jtag_clock jck displays or sets a jtag clock (tck) frequency. 15 memoryarea_set mas displays or sets memory area at command input, such as load, verify, save, memory display, or memory change.
rev. 2.0, 01/01, page 144 of 214 table 5.1 e10a hdi commands (cont) no. command abb. function 16 refresh rf updates the hdi memory information to the latest contents. 17 restart rst restarts the emulator. 18 status sts displays emulator state information. 19 step_interrupt si displays or sets the enable or disable status of interrupts during step execution. 20 trace_display td displays acquired trace buffer information. 21 ubc_mode um displays or sets ubc use states. 22 vpmap_clear vc clears the emulator address translation (vp_map) table which has been set. 23 vpmap_display vd displays the emulator address translation (vp_map) table. 24 vpmap_enable ve enables or disables the emulator address translation (vp_map) table. 25 vpmap_set vs sets emulator address translation (vp_map) table. note: support for these commands varies with the product. for the specifications of each product, refer to the online help.
rev. 2.0, 01/01, page 145 of 214 5.2.1 aud_clock:aucl description: sets or displays the aud clock (audck) values that have been set. format: aucl [

▲Up To Search▲

Price & Availability of E702196SH7750

	To Download E702196SH7750 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .